If you have setup Confluence to:
- delegate user management to JIRA (as per our documentation here) or
- use LDAP/Active directcory authentication (as per our documentation here)
Then you will need to make the following changes to your osuser.xml file:
- replace
com.atlassian.confluence.user.providers.Caching
with
bucket.user.providers.Caching
Doing this will effectively convert the following:
com.atlassian.confluence.user.providers.CachingCredentialsProvider
com.atlassian.confluence.user.providers.CachingAccessProvider
com.atlassian.confluence.user.providers.CachingProfileProvider
to
bucket.user.providers.CachingCredentialsProvider
bucket.user.providers.CachingAccessProvider
bucket.user.providers.CachingProfileProvider
- and replace
com.atlassian.confluence.user.ConfluenceHibernateConfigProvider
with
bucket.user.BucketHibernateConfigProvider
Alternatively
You can just reconfigure the new osuser.xml with your changes.
Comments (2)
Mar 10, 2006
Andrew Miller says:
Is this still valid with the new LDAP setup in 2.1.x?Is this still valid with the new LDAP setup in 2.1.x?
Mar 16, 2006
David Loeng says:
Yes, this is still relevant for upgrading to 2.1.x. (If you take a look at the o...Yes, this is still relevant for upgrading to 2.1.x. (If you take a look at the osuser.xml in 2.1.x, you'll see that it uses bucket.user.providers.CachingCredentialsProvider instead of com.atlassian.confluence.user.providers.CachingCredentialsProvider for example.
Cheers,
Dave
Add Comment