
## SAML/OAuth SSO for JSM Customers {#saml-oauth-sso-for-jsm-customers}

Introducing our most awaited add-on: [SAML/OAuth SSO for JSM Customers.](https://marketplace.atlassian.com/apps/1229212/sso-integration-with-helpdesks-for-customers?hosting=cloud&tab=overview)

&nbsp;&nbsp;

Could you imagine what it would be like if I told you that external customers can now log in via SSO to your Jira Service Management portals? We’ve got your back with our exclusive solution, SAML/OAuth SSO for JSM Customers.

### What does JSM SSO solve? {#what-does-jsm-sso-solve}

&nbsp;

If you keep your customer portal public, i.e. any anonymous user can raise a ticket on it, then there might be cases where your customer portal can be spammed by fake tickets. Managing these tickets could be very troublesome. In this scenario, Jira admins choose only the verified customers who have an account in their IDP should be allowed to raise and access tickets on the portal. Atlassian alone doesn’t allow you to do so. This is where miniOrange comes in with the JSM SSO solution.

&nbsp;

Another approach might be to add your external customer as a user in your JSM. To do so, you will have to verify his domain, and add him as a user in Jira and Atlassian access. Seems a bit tedious and expensive, yet unable to fulfill your complete requirements? miniOrange saves you from all of these hassles while fulfilling your use case.

No prerequisites required:

1. Domain Verification not required
2. Atlassian Access not required

&nbsp;

So in a nutshell, miniOrange solution, SAML/OAuth SSO for JSM Customers, is the best of both worlds. It helps in the prevention of spam ticket creation by allowing SSO for external customers and eliminating the need to add your customers as users in Jira and then grant them Atlassian access.
 
### Let’s see how? {#lets-see-how?}


With the help of our plugin your customers who are stored in any IDP (miniOrange, Okta, Azure AD, etc) will be able to login into your JSM or JSD via a link provided by our solution to the admin.
As soon as the customer clicks on the link they will be redirected to their IDP for authentication. Once authenticated the customers can raise and view the issues with ease.

A step by step user flow is explained below.

&nbsp;&nbsp;

![JSM](/blog/assets/2023/jsm.webp)

&nbsp;

The whole flow of our plugin is explained below in layman terms :

&nbsp;

1. Customer tries to access the JSM through the portal link provided by the admin. 
2. The customer will be redirected to the IDP for authentication.
3. User session is created on the portal.
4. Customers are now allowed to access and interact with the portal.
 
&nbsp;&nbsp;


It will be available across all Single Sign On protocols. We’ve already released the product with  SAML support and soon will be supporting OAuth,Open ID, and other protocols as well.

&nbsp;&nbsp;

**Upcoming Features:**

- Multiple IDP support.
- Two Factor Authentication on top of SSO.
- Domain restricted sign-up for external customers. 
- Domain based allow list for External Customer Accounts.
- Automatically adding customers to organizations based on email domain.

[Check out this link for further details.](https://miniorange.in/atlassian/sso-for-jsm-customers)




Could you imagine what it would be like if I told you that external customers can now log in via SSO to your Jira Service Management portals? We’ve got your back with our exclusive solution, SAML/OAuth SSO for JSM Customers.

SAML/OAuth SSO for JSM Customers


## Want extra features on top of Native SSO? {#want-extra-features-on-top-of-native-sso?}

[Advanced Option for Atlassian SSO Plugin](https://marketplace.atlassian.com/apps/1229209/advance-options-for-atlassian-sso?hosting=datacenter&tab=overview)

Our single sign-on feature has been an integral part of  Atlassian’s products for a prolonged time. It gives us great pleasure to say that its demand has increased manifold in the past few years.

### What makes SSO special? {#what-makes-sso-special?}

Well, the answer is pretty simple, SSO enables the users to sign in securely to their multiple independent applications. Users enter their login credentials only once that are stored in the Identity Provider.

**Is this all you need? What if you could decide how your users log in to Jira and JSM?**

We provide additional features on top of your Atlassian native SSO, miniOrange’s [advanced option for the SSO plugin](https://marketplace.atlassian.com/apps/1229209/advance-options-for-atlassian-sso?hosting=datacenter&tab=overview).

Contact Us – Drop us a mail at **info@xecurify.com** or [raise a ticket here](https://miniorange.atlassian.net/servicedesk/customer/portal/2) to talk to us.

&nbsp;&nbsp;

Since the basic use case of SSO is satisfied by the Native SSO already, hence we decided to enhance the functionality of SSO by offering two distinct features :- 

1. SSO Redirection Policy
- Default rule (redirect to URL or IDP)
- Domain based redirection
- Group based redirection
 
&nbsp;&nbsp;

2. SSO Authentication Template
- Login Template
- Logout Template

1. **SSO Redirection Policy:**
This allows the users to have a set of rules that will decide how users will log in to Jira and JSM. Depending on the configuration, you can choose which users need to be re-directed to the configured IDP or the login page. Every end-user will be required to enter the username or email address, then they will  be matched against some pre-configured rules by the admin.

- Default rule –

URL or IDP – enabling this rule will redirect your users directly to the intended URL or IDP without clicking on any buttons or links.
- Domain based redirection –

This redirects the users to the configured IDP or Jira login page on the basis of the domain of the user.
- Group based redirection –

It redirects the users to the IDP or Jira login page on the basis of the groups they belong to. 

You can set multiple rules and decide their order of priority.

&nbsp;&nbsp;

2. **SSO Authentication Template :**

&nbsp;

We understand the importance of visual aesthetic and ease of understanding! This is exactly what this feature does, it gives the flexibility to the user to design their login and logout template as per their requirement. They can make it visually appealing or     customize it as they like to.

&nbsp;&nbsp;

**Design the UI of login template:**

- Custom login template : To enhance the look and feel of login page UI custom login template will allow you to customize and display an easy-to-use login page to the end-users.
- Custom logout template : Pretty similar to login template, it can be used to change the message after the user has logged out and show any custom message.

Wait! That’s not all. We have some exciting upcoming features too 

- Advance on-the-fly group provisioning
- Manual group mapping
- Group filter
- Group regex
- Additional user properties
 
Contact Us – Drop us a mail at **info@xecurify.com** or [raise a ticket here](https://miniorange.atlassian.net/servicedesk/customer/portal/2) to talk to us.





SO enables the users to sign in securely to their multiple independent applications. Users enter their login credentials only once that are stored in the Identity Provider.