Microsoft Entra single sign-on (SSO) integration with Innoverse

In this article, you'll learn how to integrate Innoverse with Microsoft Entra ID. When you integrate Innoverse with Microsoft Entra ID, you can:

• Control in Microsoft Entra ID who has access to Innoverse.
• Enable your users to be automatically signed-in to Innoverse with their Microsoft Entra accounts.
• Manage your accounts in one central location.

To learn more about SaaS app integration with Microsoft Entra ID, see What is application access and single sign-on with Microsoft Entra ID.

The scenario outlined in this article assumes that you already have the following prerequisites:

• A Microsoft Entra user account with an active subscription. If you don't already have one, you can Create an account for free.
• One of the following roles:
  • Application Administrator
  • Cloud Application Administrator
  • Application Owner.

• Innoverse single sign-on (SSO) enabled subscription.

In this article, you configure and test Microsoft Entra SSO in a test environment.

• Innoverse supports SP and IDP initiated SSO
• Innoverse supports Just In Time user provisioning

To configure the integration of Innoverse into Microsoft Entra ID, you need to add Innoverse from the gallery to your list of managed SaaS apps.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
2. Browse to Identity > Applications > Enterprise applications > New application.
3. In the Add from the gallery section, type Innoverse in the search box.
4. Select Innoverse from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Alternatively, you can also use the Enterprise App Configuration Wizard. In this wizard, you can add an application to your tenant, add users/groups to the app, assign roles, as well as walk through the SSO configuration as well. Learn more about Microsoft 365 wizards.

Configure and test Microsoft Entra SSO with Innoverse using a test user called B.Simon. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Innoverse.

To configure and test Microsoft Entra SSO with Innoverse, complete the following building blocks:

1. Configure Microsoft Entra SSO - to enable your users to use this feature.
   1. Create a Microsoft Entra test user - to test Microsoft Entra single sign-on with B.Simon.
   2. Assign the Microsoft Entra test user - to enable B.Simon to use Microsoft Entra single sign-on.
2. Configure Innoverse SSO - to configure the single sign-on settings on application side.
   1. Create Innoverse test user - to have a counterpart of B.Simon in Innoverse that is linked to the Microsoft Entra representation of user.
3. Test SSO - to verify whether the configuration works.

Follow these steps to enable Microsoft Entra SSO.

1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.

2. Browse to Identity > Applications > Enterprise applications > Innoverse > Single sign-on.

3. On the Select a single sign-on method page, select SAML.

4. On the Set up single sign-on with SAML page, click the edit/pen icon for Basic SAML Configuration to edit the settings.

   

5. On the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:

   a. In the Identifier text box, type a URL using the following pattern: https://<domainname>.innover.se

   b. In the Reply URL text box, type a URL using the following pattern: https://<domainname>.innover.se/auth/saml2/login

6. Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:

   In the Sign-on URL text box, type a URL using the following pattern: https://<domainname>.innover.se/auth/saml2/login

   Note

   These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact Innoverse Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section.

7. Innoverse application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.

   

8. In addition to above, Innoverse application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirement.

   Expand table

   Name	Namespace	Source Attribute
   displayname	http://schemas.xmlsoap.org/ws/2005/05/identity/claims	user.userprincipalname

9. On the Set up single sign-on with SAML page, In the SAML Signing Certificate section, click copy button to copy App Federation Metadata Url and save it on your computer.

   

Follow the guidelines in the create and assign a user account quickstart to create a test user account called B.Simon.

To configure single sign-on on Innoverse side, you need to send the App Federation Metadata Url to Innoverse support team. They set this setting to have the SAML SSO connection set properly on both sides.

In this section, a user called Britta Simon is created in Innoverse. Innoverse supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Innoverse, a new one is created after authentication.

In this section, you test your Microsoft Entra single sign-on configuration using the Access Panel.

When you click the Innoverse tile in the Access Panel, you should be automatically signed in to the Innoverse for which you set up SSO. For more information about the Access Panel, see Introduction to the Access Panel.

• List of articles on How to Integrate SaaS Apps with Microsoft Entra ID

• What is application access and single sign-on with Microsoft Entra ID?

• What is Conditional Access in Microsoft Entra ID?