nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SSO Solution

nick_92pldb

Hey, community! I require your help.

I need to realize the work of SSO for JSD. I want to make it possible for my users to log in to the portal without entering their username and password. The accounts of the users are stored in AD. As far as I know, SSO for JSD is not supported, only through third-party apps (SSO integration with JIRA Service Desk – JSDSERVER-630).

Can you tell me if there is a solution for this case? But without purchasing a third-party application.

Users must access the JSD portal without entering their username and password, and without purchasing a third-party app.

Maybe there are some free apps that you can suggest to me to solve this case.

Accepted answers

Trevan Householder_Isos-Tech-Consulting_

@nick You'll need an app for this. There is currently no way to do SSO for Jira / JSD Server without an app.

Clients ask that question a lot and I always recommend this app because it just works and it's easy to configure.

Good luck!

All comments

Trevan Householder_Isos-Tech-Consulting_

@nick You'll need an app for this. There is currently no way to do SSO for Jira / JSD Server without an app.

Clients ask that question a lot and I always recommend this app because it just works and it's easy to configure.

Good luck!

nick_92pldb

@Trevan Householder_Isos-Tech-Consulting_ I didn't learn the topic very well, but what do you say about it:

Writing a custom authenticator
Jira and Confluence integrate with SSO system Seraph, the Atlassian authentication library. Seraph is a very simple, pluggable J2EE web application security framework developed by Atlassian and used in our products.
Seraph allows you to write custom authenticators that will accept the login credentials of your existing single sign-on system.
A few tips for writing your own custom authenticator for Confluence:
For Confluence 2.2 and above you must extend com.atlassian.confluence.user.ConfluenceAuthenticator instead of the Seraph DefaultAuthenticator.
The authenticator should not be a plugin. It should be placed in the class path by putting it in WEB-INF/classes or as a jar in WEB-INF/lib
The authenticator should have a public constructor that takes no arguments.
Dependency injection via setters or auto-wiring by name is not available to authenticators. Use ContainerManager.getInstance(...) instead.
The authenticators are constructed before beans are available via ContainerManager.getInstance(...), so the getInstance method needs to be called at runtime and not in the constructor.
These same restrictions apply for JIRA as well, except that:
The base class to use is com.atlassian.jira.security.login.JiraSeraphAuthenticator
Components are obtained with ComponentAccessor.getComponent(...).
Check out these examples:
CAS for Confluence, contributed by Carl Harris at Virginia Tech.
CAS for JIRA, contributed by Carl Harris at Virginia Tech.
Siteminder for Confluence, contributed by Ricardo Sueiras
There has been a discussion of integrating with Siteminder on the mailing list that may be applied to Jira integration. All third-party code must be treated with caution - always backup your Confluence instance before use. If you create a custom SSO plugin and would like to contribute it to the user community, please let us know on a support ticket. You can also browse the Seraph Discussion Forums.

Is it worth digging into this subject or will it be useless?

Andrew Laden

You may want to look at Atlassian Crowd. It is from Atlassian, so its not a third party product. Though it is a separate product and license.

It is their "enterprise" solution for single sign on across multiple Atlassian Applications. It has more integration possibilities.

Nic Brough -Adaptavist-

That is essentially "how to write your own 3rd party application". If you're willing to do that just to avoid using someone else's app, then yes, it's a good place to start.

It would be worth weighing up the reasons for not wanting a 3rd party app - if it's purely cost for example, then you are probably going to find it more expensive to employ a team to write and support this than it is to buy a 3rd party app.

nick_92pldb

Thank you! It's a sad thing that Crowd is chargeable. It looked to me that such a simple solution as SSO will be available for JSD.

nick_92pldb

Thanks for your clarification. I was hoping that such a solution as SSO will be available to JSD for free or will be integrated into the product.

Trevan Householder_Isos-Tech-Consulting_

Crowd works great, but you'll need to know that JSD customers added to Crowd consume a Crowd license (not a JSD license, but a Crowd license).

https://community.atlassian.com/t5/Crowd-questions/JSD-customers-are-counted-for-crowd-licensing-during-SSO/qaq-p/805133

https://jira.atlassian.com/browse/CWD-4116?_ga=2.234719194.590685323.1597185092-1551811082.1597088881

For this reason, some companies use Okta so they don't have to pay for Crowd licenses for Customers.

nick_92pldb

@Trevan Householder_Isos-Tech-Consulting_could you give me a quick link to Okta? Is it an app or something else?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk

jira-service-desk-server

sso