I see, that's unfortunate. The lack of a migration for repository user accounts throws a wrench into our upgrade plans. Even beyond user attributes and security settings, those repository users have Forms user tasks they are currently working on, and if I'm reading your linked page correctly, it sounds like once we switch Forms to use Directory Server authentication, those user tasks will basically become orphaned since their associated user accounts will no longer be valid. And there is no way to tell Forms to get the user accounts both from an LF repository and the Directory Server - it has to be one or the other (which basically means if you purchase Employee Participant licenses for an existing Rio system, you are forced into this change if you want to be able to use them).
I can't imagine we are the only folks who have run into this scenario. Back when LF was first deployed, Directory Service had not been released yet, so their configuration is heavily invested in repository named users. Are there plans to offer a smoother migration method?