We are interested into setting up and using the new SAML identity providers in JSM for portal only customers, so that our customers could use existing b2c credentials to access JSM too.
Thing is, these customers already exist in JSM.
Is there a way to combine them together?
Or move a portal only (username and pw) user to be managed via the new identity provider?
Will a user with the same email now logging in via a new ID provider inherit all his previous issues?
I understand that you want your portal-only customers to use their existing Azure B2C credentials to access the JSM portal while retaining access to their previous tickets.
We have a solution using which we can effectively meet these requirements. It will allow you to keep your current Identity Provider, enabling customers to raise new tickets and access their previous ones without needing to switch to a new provider.
If you would like a demo of the app please raise a service request here and a miniOrange representative will help you with all the details.
PS: I work for miniOrange, One of the Security vendors in Atlassian Marketplace.
Thanks,
Aditya
Hello,
Certainly! It’s great that you’re looking to set up SAML identity providers in Jira Service Management (JSM) for your portal-only customers. Let’s break down your questions:
Combining Existing Customers with SAML Identity Providers:
Yes, you can combine existing portal-only customers with the new SAML identity providers. When you configure SAML single sign-on (SSO) for JSM, existing portal-only users can authenticate through your organization’s identity provider.
Follow the instructions to add an identity provider to Jira Service Management. This process allows you to secure customers with access to your help center using SAML SSO.
Note that this is separate from adding an IdP for internal users.
Moving Portal-Only Users to the New Identity Provider:
You can transition a portal-only user (who currently uses a username and password) to be managed via the new SAML identity provider.
Configure SAML SSO following the instructions provided here.
Once set up, the user will log in via the new ID provider, and their existing account will be associated with it.
Inheriting Previous Issues:
When a user with the same email logs in via the new ID provider, their previous issues will remain intact. The transition to SAML SSO won’t affect their issue history.
Remember to follow the specific steps outlined in the Atlassian documentation to ensure a smooth setup. If you encounter any issues during the process, feel free to ask for further assistance. MyCenturaHealth Org
Best Regards
misty569
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.