How to enable SSO in jenkins using crowd

[Manjul Srivastava]

I have integrated crowd and jenkins using crowd 2 plugin in jenkins, and centralized user management using crowd is working.

But i am stucked with SSO functionality.

[Manjul Srivastava · Accepted solution]

I have set session validation to 0. Now its working fine

[Nic Brough [Adaptavist]]

"It doesn't work" is not really very helpful as a question. You need to give details. What have you configured? What are the symptoms? What documentation did you follow and where did you do things differently from what the docs said? What do your logs say?

[Manjul Srivastava]

Hi Nic,

I have crowd and jenkins on same machine at ports 8095 and 8090. On jenkins i installed crowd 2 plugin.

I have set machine's IPAdress as sso domain in crowd.

I copied main library crowd-integration-client-2.7.1.jar and all other supporting jar from crowd's client folder to jenkins's WEB-INF/lib folder.

I copied crowd.properties file from crowd's client/conf folder and paste it into WEB-INF/classes and edit it with details

application.name jenkins

application.password jenkins

application.login.url http://IP:8090

crowd.server.url http://IP:8095/crowd/services/

crowd.base.url http://IP:8095/crowd/

session.isauthenticated session.isauthenticated

session.tokenkey crowd.token_key

session.validationinterval 2

session.lastvalidation session.lastvalidation

And done all configuration in jenkins's crowd part in security section.

enable SSO

set cokie.domain with IPAdress of machine

set cokie.tokenkey as crowd.token_key

After all these configuration i restart my jenkins

Now, problem that i am facing is when ever i login in or logout from jenkins it get reflects on crowd but when ever i do the same in crowd it do not get reflected on jenkins. Users are same.

[Manjul Srivastava]

Basically, i noticed that session created for any jenkins user do not get expire with other atlassian tools when someone logout from jira/stash/any other atlassian tool.

But when i logout from jenkins it get reflected on other tools.

[stuartej]

is this officially documented anywhere? My jenkins deployment runs with the following /usr/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8082 --ajp13Port=-1 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 --prefix=/jenkins The war file is managed by RPM from Jenkins LTS, i assume on restart it unpacks it into the /var/cache/jenkins/war directory, however my concern is it is only cache directory and on shutdown/restart/update any changes i may apply could get blitzed I assume the proper location to put these auxilary components would be somewhere in /var/lib/jenkins