Configure and test Microsoft Entra SSO for Allbound SSO
Configure and test Microsoft Entra SSO with Allbound SSO 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 Allbound SSO.
To configure and test Microsoft Entra SSO with Allbound SSO, perform the following steps:
Browse to Identity > Applications > Enterprise applications > Allbound SSO > Single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration section, If you wish to configure the application in IDP initiated mode, perform the following steps:
a. In the Identifier text box, type a URL using the following pattern:
https://<SUBDOMAIN>.allbound.com/
b. In the Reply URL text box, type a URL using the following pattern:
https://<SUBDOMAIN>.allbound.com/acs
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://<SUBDOMAIN>.allbound.com/
Pastaba
These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact Allbound SSO Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section.
On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, click Download to download the Federation Metadata XML from the given options as per your requirement and save it on your computer.
On the Set up Allbound SSO section, copy the appropriate URL(s) as per your requirement.
Create a Microsoft Entra test user
In this section, you'll create a test user called B.Simon.
In the app's overview page, select Users and groups.
Select Add user/group, then select Users and groups in the Add Assignment dialog.
In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
In the Add Assignment dialog, click the Assign button.
Configure Allbound SSO
To configure single sign-on on Allbound SSO side, you need to send the downloaded Federation Metadata XML and appropriate copied URLs from the application configuration to Allbound SSO support team. They set this setting to have the SAML SSO connection set properly on both sides.
Create Allbound SSO test user
In this section, a user called Britta Simon is created in Allbound SSO. Allbound SSO 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 Allbound SSO, a new one is created after authentication.
In this section, you test your Microsoft Entra single sign-on configuration with following options.
SP initiated:
Click on Test this application, this will redirect to Allbound SSO Sign on URL where you can initiate the login flow.
Go to Allbound SSO Sign-on URL directly and initiate the login flow from there.
IDP initiated:
Click on Test this application, and you should be automatically signed in to the Allbound SSO for which you set up the SSO.
You can also use Microsoft My Apps to test the application in any mode. When you click the Allbound SSO tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Allbound SSO for which you set up the SSO. For more information, see Microsoft Entra My Apps.
Distribuire e monitorare le applicazioni aziendali nelle soluzioni Azure è utile per garantire la sicurezza. Questo modulo illustra come distribuire agli utenti app locali e basate sul cloud.
Illustrare le funzionalità di Microsoft Entra ID per modernizzare le soluzioni di identità, implementare soluzioni ibride e implementare la governance delle identità.