Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

crowd properties fail #3

Open
BraunreutherA opened this issue May 16, 2015 · 3 comments
Open

crowd properties fail #3

BraunreutherA opened this issue May 16, 2015 · 3 comments

Comments

@BraunreutherA
Copy link

Hi,

I installed crowd and at the step of logging into the crowd console I get the following error: Connection to authentication server failed. Please review the logs for more information.

I went into the crowd container an changed the crowd.properties file to some modifications recommended at the atlassian forums but this doesn't work. How did you get it running?

at the logs this error occurs:

unable to unset crowd sso token

@giovannicandido
Copy link
Member

I remember a problem with how crowd process auth from IP Address. I should have documented but anyway:
By default it allows only a certain class of ips, localhost is one of then. The problem is docker containers run on virtual networks in the host, so the crowd application do not run in localhost when the proxy is used.

To work around, the first login should be direct in the crowd port exposed by the container, the port is 8095. Then it should be configured to allow a class of ips to authenticate, the class could be different for any installation. Use crane status to show the containers ip's and configure crowd to permit login from then.

In my case a have:

172.17.0.38
172.17.0.86
172.17.0.40
and so on

So I open for 172.17.*.* because other containers (jira, stash, etc...) will authenticate too

See: https://confluence.atlassian.com/display/CROWD/Specifying+an+Application%27s+Address+or+Hostname

@BraunreutherA
Copy link
Author

Thank, that worked.

I had to go into the crowd container in /opt/crowd-home and edit the crowd.properties file. Just change the server url and auth url for sub.domain.com to the ip crane status gives you for your crowd application with the port 8095.
Then you can log in and add the other apps.

@giovannicandido
Copy link
Member

I don't knew it could be changed in crowd.properties file. I will update the script to automate this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants