Hi, I am testing our JIRA upgrade from 4.2 to 4.4. In 4.2, all our users were internal and LDAP was used for authentication when the username matched one found in LDAP. As you may know, in the process of the upgrade, JIRA 4.3-4.4 reads the old osuser.xml file and applies directory settings to its new user management design. The question I have is -- what happens to all the users that aren't picked up by the reading of osuser.xml and end up as JIRA internal users. For instance, it might be a terminated user that gets rehired, and I want to reapply his JIRA account to the LDAP authentication model instead of it staying as internal user. Ideally I'd be happy to go back to the 4.2 model where all our users were internal and the ones that existed in LDAP used the external LDAP password. Any ideas?
If you re-add the user in your LDAP directory, while making sure the LDAP server is first in your user directory listing order, next time they login JIRA will search the LDAP server first, since it takes precedence. This should make the switch for that user account to now be associated with the LDAP user directory. Note: Its possible group memberships will be lost during this migration.
Script Runner plugin is a handy tool for renaming/merging users in JIRA:
https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/version/310
Cheers,
Pelle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.