Crowd administrator login not working

[KMcKenzie]

Hi guys,

We have configured Crowd to control Jira, FE/CR authentication through LDAP. Everything was working fine until we got an error HTTP Status 404 - /crowd/console/login.action is not available. Our system admin restarted the application. Now Crowd is up but we cannot log into Crowd using Crowds internal admin password “Invalid login” and LDAP users are not being authenticated in other applications.

The problem is we have not enabled our mail server (still in the early stages of testing), so we are unable to reset the admin password and there are no other users setup in Crowd hence we have no way of logging into Crowd.

Any idea why this would happen and how to fix this?

Thanks,

Kaitlin

[Sultan Maiyaki]

Hi Kaitlin,

Can you provide some part or full atlassian-crowd.log located in the crowd home? This should give a better idea of the issue.

[KMcKenzie]

Hi Sultan,

Here is part of the atlassian-crowd.log:

2013-05-22 15:34:36,992 http-8095-6 ERROR [crowd.console.action.Login] Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Server returned error code = 404 for URI : http://lappmab00035t05:8095/crowd/services/SecurityServer. Check server logs for details
org.springframework.security.authentication.AuthenticationServiceException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Server returned error code = 404 for URI : http://lappmab00035t05:8095/crowd/services/SecurityServer.

Caused by: org.codehaus.xfire.XFireRuntimeException: Server returned error code = 404 for URI : http://lappmab00035t05:8095/crowd/services/SecurityServer. Check server logs for details
at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:130)
at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
... 74 more

Thanks,

Kaitlin

[Sultan Maiyaki]

Hi Kaitlin,

The problem is happening because the Crowd Client can't resolve the Crowd Server's URL, even if it can be resolved by other clients (ie. browser). Please edit the crowd.properties file located in your Home-Directory folder (defined at <Crowd-Install>/crowd-webapp/WEB-INF/classes/crowd-init.properties) so that it can resolve the URL locally:

Replace:

crowd.server.url=http://lappmab00035t05:8095/crowd/services

With:

crowd.server.url=http\://localhost\:8095/crowd/services/

You can also use the ip based rather than localhost if you so wish. Ensure that the port number is correct. You will need to restart crowd for the changes to take effect

[Sultan Maiyaki]

Hi Kaitlin,

The problem is happening because the Crowd Client can't resolve the Crowd Server's URL, even if it can be resolved by other clients (ie. browser). Please edit the crowd.properties file located in your Home-Directory folder (defined at <Crowd-Install>/crowd-webapp/WEB-INF/classes/crowd-init.properties) so that it can resolve the URL locally:

Replace:

crowd.server.url=http://lappmab00035t05:8095/crowd/services/

With:

crowd.server.url=http\://localhost\:8095/crowd/services/

You can also use the ip based rather than localhost if you so wish. Ensure tht the port number is correct. You will need to restart crowd for the changes to take effect

Sorry that my previous comment was not well formed by the macro

Regards,

Sultan

[Ansar Rezaei]

Hi
I have same problem.
My main crowd running on 192.168.100.21 and I need an evaluation server behind this. when I import crowd xml backup of 21 into 29, I was not able to login. I open xml backup using e text editor and replace all 21s with 29 and the problem has been resolved. 

[Jim Pickering]

If it doesn't work, clear your browser cookies then try it again. It caches the previous incorrect path, despite making the suggested change above.

[Ryan Goodwin]

Doesn't work. Using private browsing sessions and caches emptied. Brand new crowd installation.

[Filip Andersson]

I had the same error and tried updating the crowd.properties file as suggested but I am still getting authentication error. Is this and accepted answer?

[Ryan Goodwin]

Same issue here. My crowd properties file was auto configured on setup and looks exactly like the suggestion and i'm getting this error.