Can't log in in Crowd after adding trusted proxies

Question

Hi, I've set up Crowd to run behind Apache HTTP and to get Crowd to use the IP address from the calls from applications (Jira, BitBucket, etc). I added 127.0.0.1 and 0:0:0:0:0:0:0:1 as trusted proxies. After doing so all calls from the applications works just fine, but when I can't no longer log in to Crowd as a user or admin. Then I enter username and password I just gets redirected to the log in page again with no error message. This is what appears in the log when I try to authenticate with my user 'heka': 2018-07-10 11:29:34,238 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Trying to authenticate user heka in directory Crowd server (163841) for application crowd 2018-07-10 11:29:34,240 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] User heka does not exist in directory Crowd server (163841), continuing 2018-07-10 11:29:34,240 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Trying to authenticate user heka in directory Pulsen AD (557057) for application crowd 2018-07-10 11:29:34,315 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Authenticated user heka in directory Pulsen AD (557057) for application crowd 2018-07-10 11:29:34,324 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Located user 'heka' in directory 557057 'Pulsen AD' 2018-07-10 11:29:34,350 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Storing user attributes for user and application 2018-07-10 11:29:34,402 http-nio-8095-exec-17 DEBUG [crowd.manager.application.ApplicationServiceGeneric] Located user 'heka' in directory 557057 'Pulsen AD' As I can't access the GUI I managed to remove the trusted proxies from the database and after restarting crowd I can log in again, but then all request from applications fail... Regards, Henrik Karlsson

AnnWorley · Answer

Hi Henrik,

If you have SSO enabled the resolutions in this article may help: Redirected to the login screen with no errors when attempting to log in to any Atlassian applications

It says the most common cause of the behavior is browser caching so please clear your browser cache first.

The article mentions this symptom which is similar to yours:

No errors thrown in the application's logs or Crowd's logs, or in the UI. In fact, based on the logs, authentication should be successful

This entry you posted looks like a successful login to Crowd from an external Active Directory user directory:

Authenticated user heka in directory Pulsen AD (557057) for application crowd

Thanks,

Ann