[Episode 1] SSO Challenges in Jira: A Business Perspective and Discussion!

[Ananjan_Mishra]

Hello Community peeps!

I'm starting a new bi-weekly series of articles where I'll be sharing both common and out-of-the-box use cases found in the Atlassian ecosystem. This is the first of many, and I'm really looking forward to sharing more with you!

Today, let's dive into an intriguing business solution that combines Service Desk and Jira users—a challenge that many Atlassian admins might relate to. No beating around the bush, let's get right into it.

In a recent project, we faced a unique requirement involving Single Sign-On (SSO) and redirection rules for Jira. The setup included two URLs: a base URL and an alias. Here's what we tackled:

• Jira Access: SSO was needed only for URL 1 (base URL).

• Service Desk Access: SSO was required for both URL1 and URL2 (alias URL).

• Redirection Rules:

  • URL1 directs users to IDP1 (e.g., Okta).

  • URL2 directs users to IDP2 (e.g., Azure AD).

To solve this, we customized our JIRA OAuth SSO app. This version lets you configure a Custom Base URL and set specific redirection rules for the Service Desk based on this custom URL.

Implementation was seamless: users accessing URL1 were redirected to IDP1 (e.g., Okta), while those on URL2 went to IDP2 (e.g., Azure AD). This setup ensured a smooth user experience while maintaining security.

So, that’s one of the business use cases! If you find this business challenge interesting or relevant, please like the article and feel free to comment with any questions. I'm here to answer!

Stay tuned for the next one🚀

[Matt Doar _Adaptavist_]

Is there a link to the actual article?

[Ananjan_Mishra]

Hey Matt!

This is the actual article itself! We have our app in the Atlassian marketplace, and we recently made a custom solution for one of our customers. If you'd like more details, just open a ticket here, and we can set up a quick call to walk you through the specifics of the use case!