I’m working on integrating our development tools and want to centralize user management. Right now we’re deploying JIRA, Confluence, and Jenkins in our environment.
Instead of maintaining separate user accounts across all these platforms, I’d prefer to have a single authentication source. I know that Jenkins supports Atlassian Crowd for user authentication and authorization. I also understand that Confluence can connect to both Crowd and JIRA for managing users.
My question is whether Jenkins can directly connect to JIRA for user authentication and authorization, bypassing Crowd entirely. Is there a way to configure Jenkins to validate user credentials against JIRA’s user database without needing Crowd as an intermediary?
Has anyone successfully set up this type of integration between Jenkins and JIRA for user management?
Hit this same issue six months back - we wanted to skip Crowd licensing too. Jenkins can’t authenticate directly against JIRA’s user store, but OAuth2 works as a workaround. We used the Generic OAuth plugin and set up JIRA as the provider. You’ll need to configure application links in JIRA and handle OAuth tokens manually, but you get SSO. Users log in through JIRA, Jenkins gets the auth tokens. Not as smooth as Crowd would be, but way better than managing separate accounts everywhere. Only catch is you’ll still need to map user permissions manually between systems.
i’ve heard that skippin Crowd can be tricky. Jenkins can use LDAP if JIRA’s set up for it, otherwise, your best bet might be the JIRA plugin. but it seems like Crowd really makes things easier with the auth process. just my 2 cents!
No Jenkins plugin can directly authenticate against JIRA’s internal user database. Jenkins supports LDAP, Active Directory, and SSO, but JIRA integration needs workarounds. I’ve had the best luck setting up both Jenkins and JIRA to use the same LDAP directory. You’ll get centralized auth without paying for Crowd licenses. Just make sure JIRA’s configured for external LDAP instead of its internal directory. Another option is SAML SSO with an identity provider both tools can use. That scales better if you’re planning to add more tools later. Crowd’s still the easiest route for Atlassian integration, but these alternatives work great if budget’s tight.