How can I provision users from our own single sign-on service to OPSWAT Central Management?
OPSWAT Central Management offers 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 OPSWAT Central Management console through your own SSO service, OPSWAT Central Management will provision that user as a read-only user on your account. You can update the user's role later.
OPSWAT Central Management 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, go to your identity provider's website and follow the instructions to configure a SSO application for OPSWAT Central Management.
To integrate OPSWAT Central Management with your own SSO service:
- Log into the OPSWAT Central Management console with admin permissions.
- Navigate to Settings > Integrations > Single sign-on.
- Select Enable Single Sign On checkbox.
- Enter an IdP Name. This is for your reference
- Click the Choose File button to upload an IdP X.509 certificate .pem file that you received from the Identity Provider.
- Enter the Issuer information you received earlier from the identity provider
- Enter the IdP SSO URL you received earlier from the identity provider
- Enter the IdP Log out URL and Error URL you received earlier from the identity provider if any.
- Click the Save button.
- After you save your changes successfully, OPSWAT Central Management will a OPSWAT Central Management Login URL You must copy this URL and update a postback SSO URL (also called the Assertion Consumer Service URL) of the SSO application for OPSWAT Central Management in your identity provider.
Note: You can import information from step #5 through #8 from the IdP metadata file that you received earlier from the identity provider if it is available.
You can find detailed setup guideline for specific identity providers here from MetaAccess documentation. OCM and MetaAccess has the same configuration for SSO log into the console management, therefore you can follow guidelines there.