[#CONF-9195] Confluence 2.5.6 ldap configuration failing on osuser2atluser.jsp migration

Confluence

Confluence 2.5.6 ldap configuration failing on osuser2atluser.jsp migration

Created: 16/Aug/07 07:26 PM Updated: 02/Oct/07 07:15 PM

Component/s:

External User Management

Affects Version/s:

2.5.6

Fix Version/s:

2.5.8, 2.6.0, 2.7

Time Tracking:

Original Estimate:

1 day

Remaining Estimate:

1 day

Time Spent:

Not Specified

File Attachments:

atlassian-confluence.log (59 kB)
2.

atlassian-user-confluence-2.5.x-1.9.jar (271 kB)

Image Attachments:

1. Picture 1.png
(144 kB)

Environment:

« Hide

Testing environment (also did it with hsqldb):

System Date Thursday, 16 Aug 2007
System Time 17:24:36
System Favourite Colour Myrtle
Java Version 1.5.0_07
Java Vendor Apple Computer, Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0_07-87
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name jeremy
User Timezone America/Los_Angeles
Operating System Mac OS X 10.4.10
OS Architecture i386
Filesystem Encoding MacRoman

Java VM Memory Statistics
Total Memory 127 MB
Free Memory 65 MB
Used Memory 62 MB
Memory Graph
[Used Memory (50 %)] [Free Memory (50 %)]
50 % Free

Runtime Information
Database Dialect com.atlassian.hibernate.dialect.MySQLDialect
Database Connection URL jdbc:mysql://localhost/confluence256?autoReconnect=true
Database Driver Name com.mysql.jdbc.Driver
Database Driver Version 5.0
Application Server Apache Tomcat/5.5.15
Servlet Version 2.4
Confluence Home /Users/jeremy/oldConf/confhome256
Uptime 5 minutes, 58 seconds
Confluence Version 2.5.6
Build Number 812

Issue Links:

Blocker

This issue blocks:

~~CONF-9307~~ Errors during user migration process

Reference

This issue relates to:

~~CONF-9117~~ Confluence API supports adding user with null password, but users will null passwords produce NullPointerException when using the osuser to atlassian-user migration utility jsp

Participants:	Aaron Hossain, Aleksandar Cvetkovic, Ben Jones, Jeremy Largman [Atlassian], Johan van den Hoven, Matt Ryall [Atlassian], Matthew Jensen [Atlassian] and Per Fragemann [Atlassian]
Since last comment:	1 year, 1 week, 3 days ago
Resolution Date:	27/Sep/07 09:21 PM
Support reference count:	12
Labels:

Description

« Hide

When doing step 5 from http://confluence.atlassian.com/display/CONF256/Add+LDAP+Integration, the attached error is displayed.

This will migrate your existing users.

Begin migration.
Migrating users ... ERROR

    User [jla] already exists in OSUser Repository
    If you are upgrading from Confluence 2.1.x and have already performed this migration previously - you do not need to perform this again. You only need to move your settings over as outlined in this document.
    Otherwise, please ensure that in your:

    confluence/WEB-INF/classes/atlassian-user.xml

    file, that the hibernateRepository is first and the osuserRepository is second.

The problem is that when you try step 6, you can't log in with your hibernate user, so even if the ldap integration works, you can't assign global permissions to groups.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeremy Largman [Atlassian] added a comment - 17/Aug/07 05:37 PM

log ith atlassian user login enabled

[ Permlink | « Hide ]

Jeremy Largman [Atlassian] added a comment - 17/Aug/07 05:38 PM - edited

So far the workaround is to install 2.5.5, complete the ldap integration, then upgrade to 2.5.6 (or later).

you could add:

to atlassian-user.xml so that step #6 works. While this might be ok for an evaluation version, it is not recommended for production.

Workaround #1 is preferable.

[ Permlink | « Hide ]

Per Fragemann [Atlassian] added a comment - 24/Aug/07 04:40 AM

the fix version was not realistic anymore, because the 2.5.6 has been released already. setting to 2.5.x

[ Permlink | « Hide ]

Matt Ryall [Atlassian] added a comment - 31/Aug/07 12:19 AM

Looks like a serious problem, and we saw this on c.a.c migration. Raising priority.

[ Permlink | « Hide ]

Johan van den Hoven added a comment - 05/Sep/07 02:20 PM

Installing Confluence 2.5.5 enabled us to complete the user migration succesfully!

[ Permlink | « Hide ]

Johan van den Hoven added a comment - 05/Sep/07 02:21 PM

https://support.atlassian.com/browse/CSP-10302

[ Permlink | « Hide ]

Ben Jones added a comment - 16/Sep/07 08:21 PM

I called Ivan from Support last Thursday and was told we'd have a fix for this uploaded to the issue by Friday. Haven't seen anything further done for this issue. I have installed 2.5.7(which has exactly the same problem). Will the patched JAR file be attached to the issue today?

[ Permlink | « Hide ]

Matt Ryall [Atlassian] added a comment - 17/Sep/07 12:56 AM

Hi Ben,

Our bug-fixing team is working on this issue at the moment. We'll let you know as soon as we have a patch ready.

Given current progress, it will be a few more days before we have completed the work and tested it thoroughly. Sorry for the delay.

Regards,
Matt

[ Permlink | « Hide ]

Aleksandar Cvetkovic added a comment - 17/Sep/07 10:08 AM

We need the patch too...

[ Permlink | « Hide ]

Jeremy Largman [Atlassian] added a comment - 17/Sep/07 01:46 PM

One more workaround, submitted by a user:

Actually I worked around the issue in a different way....

With only hibernate repository installed there are no existing users or
groups but you can still log in using the 'sign up' feature. This
creates a normal user account and also creates the confluence-users
group in the hibernate repository.

Next add the osuser repository back in the atlassian-user.xml, keeping
the hibernate repository active. Now you can log in with the (osuser)
admin account. Elevate the hibernate account you created in the first
step to a confluence administrator by adding 'administer confluence'
rights to the individual account, then log out.

Now remove the osuser repository again, leaving only the hibernate
repository. Log in with the new administrator account. Create a new
confluence-administrators group and make the new account a member.

Now you can add the ldap repository. Everything seems to work from
here. Newly authenticated ldap users can be added to the
confluence-users group and everything seems to work (so far...)

[ Permlink | « Hide ]

Aaron Hossain added a comment - 19/Sep/07 06:51 AM

Dont fancy downgrading applying migration then upgrading again, sounds like a sure fire way to break your install !!

Will wait for a bug fix.

[ Permlink | « Hide ]

Matthew Jensen [Atlassian] added a comment - 24/Sep/07 10:06 PM

Patched atlassian-user.

[ Permlink | « Hide ]

Matthew Jensen [Atlassian] added a comment - 24/Sep/07 10:10 PM

The attached atlassian-user JAR includes a fix for this issue in Confluence 2.5.6 and 2.5.7. To install it, please do the following:

shut down Confluence
put the attached JAR, 'atlassian-user-confluence-2.5.x-1.9.jar', into confluence/WEB-INF/lib/
remove the old atlassian-user JAR from confluence/WEB-INF/lib/ (it should be called 'atlassian-user-1.5-stable-compatible-1.jar')
start up Confluence again.

If you still experience the problem after restarting Confluence with this new JAR, please attach a copy of the complete stack trace to this issue.

[ Permlink | « Hide ]

Matthew Jensen [Atlassian] added a comment - 27/Sep/07 09:21 PM

Fixed in all versions of atlassian-user now so that means all confluence versions as well (2.5.x, 2.6.x and 2.7.x development branches).