This article describes setting up single sign-on (SSO) with Okta. This feature must be enabled in your account by a MetaLocator support technician in order to function as shown in this article.
Step 1. Configure the Account
Login as the Account Owner and go to My User Profile
Scroll down and expand Show Advanced Options, then update the following options according to your Okta settings.
onelogin_saml_idp_domain
Set this to the domain associated with your email address, e.g. customer.com. This ensures that the anonymous link on our login form knows which SSO to invoke based on an incoming email.
Within Okta, create a new App called "MetaLocator", with the following SSO URL. This is also known as the ACS URL.
https://admin.metalocator.com/plugins/user/oneloginsaml/oneloginsaml.php?acs=&id=XXXXX
Where XXXXX is your primary account owner's User ID as shown below:
Service Provider Entity ID should be
metalocator-saml
Users will be created on the fly based on the email address coming from Okta. The accounts will be created as "blocked" accounts with no access to any MetaLocator features. The requesting user will receive an email notification that their account is pending review and the account owner will receive an email notification that an account is pending review as shown below:
Click the link provided and login as the account owner. Click the username to edit the user. Choose an appropriate user type:
Click Save, then enable the user as shown below. This triggers an email notification to the new SSO user indicating that their login has been enabled.
The email notification is shown below.
When the user logs in, they will now see the resources available to them, based on the type of user chosen above.
Name ID format
If required, the Name ID format is:
urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified