Single Sign-On (SSO) activity can be tracked within Enable to verify login attempts.
This article will guide you through tracking SSO in Enable.
Looking for something else?
-
Not yet configured SSO with your identity provider? Learn how to set up SSO here.
Tracking SSO in Enable
Channel admin users have access to the Config area and user activity log within Enable.
To track SSO login for users in Enable:
Step 1: Click on Config in the green banner at the top of the page.
Step 2: Click on Users in the drop-down menu.
Step 3: Click on the Activity tab.
Step 4: Select the following filters:
- Trading partner: Ensure that no trading partner (e.g. customer/supplier) is selected.
- Activity type: Select SAML2 single sign-on, Log in, and Log out. Click OK.
Step 5: Click on the Preview button.
Step 6: Review the user login attempts in the log to see who has succeeded or failed to log in to Enable. Ensure you review the method used in the Activity type column; SAML2 will indicate that SSO was used.
Tip: Hover over the Failure activity indicator to display more details. For example, if a login attempt has failed, this may display the email address of a user who has attempted but failed to sign in.
Note: If any successful SAML2 activities exist, any issues other users are experiencing with SSO are likely to be specific to the user or their browser rather than SSO configuration. If no SAML2 activities exist, SSO requests aren’t being received by Enable which is likely to be caused by configuration issues with your identity provider. Learn more about configuration and troubleshooting here.
Once you have confirmed that SSO is working, Enable can enforce sign-in through SSO only, and remove the option of manual login with your current Enable passwords. If this is required by your organization, reach out to the Enable Support team.
What’s next?
Ready to learn more about the user activity log now that SSO setup is complete? Learn more about monitoring user activity here.
Experiencing other SSO issues? Learn more about testing and troubleshooting SSO here.