You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
I have set session validation to 0. Now its working fine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.