How can I provision users from Microsoft Azure to MetaAccess?

MetaAccess offers an integration with a 3rd-party Single Sign-on Service (SSO). This enables an account to provision new users to manage your account. When a user logs into the MetaAccess console through your own SSO service, MetaAccess will provision that user as a read-only user on your account. You can update the user's role later.

MetaAccess uses the secure and widely adopted industry standard Security Assertion Markup Language 2.0 (SAML 2.0), so that you can integrate easily with any large identity provider that supports SAML 2.0.

To get started, log into Azure Portal and create an application for MetaAccess. Details can be found here

1. Log into Azure Portal as an administrator

2. Navigate to Azure Active Directory > Enterprise applications

3. Click the + New Application

images/download/attachments/4079815/image2020-2-11_15-19-44.png

4. select Non-gallery application

images/download/attachments/4079815/image2020-2-11_15-15-4.png

5. Enter Application name, for example MetaAccess

6. Under the Getting Started section, select 2. Set up Single sign on

images/download/attachments/4079815/Screen_Shot_2020-02-11_at_3.44.02_PM.png

7. Click Edit icon ( images/download/thumbnails/4079815/Screen_Shot_2020-02-11_at_3.32.34_PM.png ) on Basic SAML Configuration. Enter https://gears.opswat.com as a placeholder for all parameters. Click Save.

images/download/attachments/4079815/Screen_Shot_2020-02-11_at_3.21.49_PM.png

8. Click Edit icon ( images/download/thumbnails/4079815/Screen_Shot_2020-02-11_at_3.32.34_PM.png ) on User Attributes & Claims: configure Unique User Identifier (Name ID) format as EmailFormat and its value as a user's email by clicking on that claim and choose its format as email address and source attribute as user.mail or user.localprinciplename

images/download/attachments/4079815/image2020-2-11_15-35-4.png

images/download/attachments/4079815/Screen_Shot_2020-02-11_at_3.36.03_PM.png

9. On SAML Signing Certificate section, you can now download the IdP configuration xml file by downloading Federation Metadata XML (for example, azure.xml). You can use this file to import to MetaAccess

images/download/attachments/4079815/image2020-2-11_15-42-43.png

10. (Optional) Get additional information

a. Download Azure’s certificate

images/download/attachments/4079815/image2021-6-2_15-45-59.png

b. Get Azure Login URL

images/download/attachments/4079815/image2021-6-2_15-46-16.png

c. Get Azure AD Identifier

images/download/attachments/4079815/image2021-6-2_15-46-32.png

Configure Microsoft Azure on MetaAccess:

11. Log into the MetaAccess console with an admin permission

12. Navigate to User management > SSO

13. On Control tab, enable "Enable Single Sign On" checkbox

14. Enter an IdP Name, for example: Azure

15. Click Choose File to import the identity provider metadata you got earlier in step #9 . Select the file you saved in step #9, Azure.xml. If the file is valid then IdP certificate, Issuer, and IdP SSO URL will pop up. Click SAVE

16. ( Optional) Use this step if you can not import the metadata file

a. IdP Certificate: Upload the certificate downloaded in Step 10.a

b. Issuer: Use the value got in Step 10.c

c. IdP SSO URL: Use the value got in Step 10.b

17. After you save your changes successfully, MetaAccess generates a MetaAccess Login URL. Copy this URL to import to Microsoft Azure

images/download/attachments/4079815/image2021-3-17_16-22-0.png

Update MetaAccess app on Microsoft Azure

18. Switch to Azure Portal

19. Navigate to the application you created earlier, MetaAccess, click Edit icon on Basic SAML Configuration. Replace value of Reply URL (Assertion Consumer Service URL) and Relay State with the MetaAccess Login URL you copied in step 17 then click Save.

images/download/attachments/4079815/Screen_Shot_2020-02-11_at_4.12.12_PM.png

DONE. Now you need to assign people/groups who can access MetaAccess on Microsoft Azure and test the configuration. Check out our FAQ if you get an error when a user logs into MetaAccess

If You couldn't import the identity provider information from the IdP metadata file, you can get information from the Set up instruction page of the app and copy IdP certificate, Issuer, and IdP SSO URL to the MetaAccess console