This information applies to SwaggerHub On-Premise.
SwaggerHub On-Premise supports single sign-on (SSO) for authenticating users. We support single sign-on via Okta (SAML 2.0), Active Directory, OpenLDAP, and GitHub.
To learn how to configure single sign-on in SwaggerHub On-Premise, see:
SAML settings for other SAML 2.0 identity providers
|Note:||In versions prior to 1.20.1, SSO setup included an extra step to migrate the existing users to SSO. Starting from v. 1.20.1, the users are migrated automatically, and the manual migration procedure is no longer needed.|
Before enabling SAML or LDAP SSO, review the user list on the License page of the Admin Center and make sure the email addresses of all the existing users (including you, the admin) are the same as in your identity provider.
Users with non-matching email addresses will have to update the email address in their SwaggerHub settings. Otherwise, SSO logins will not be linked to those existing users, and SwaggerHub will create new users.
After SSO has been enabled in SwaggerHub, all the users must log in via SSO from now on. SwaggerHub supports both SP-initiated login (when a user clicks Log in on the SwaggerHub home page) and IdP-initiated login (when a user navigates to SwaggerHub from the application directory on the identity provider’s site).
SwaggerHub supports just-in-time user provisioning. New users will be created in SwaggerHub the first time they log in after being authenticated by the SSO provider.
Username and email considerations
Email as identification
SwaggerHub uses email addresses to identify users internally. Make sure the addresses of SSO users do not change. If a user’s email address changes, SwaggerHub will not be able to find an existing user in the database and will create a new user instead.
If you need to update the email addresses of SSO users, please contact Support.
SwaggerHub usernames for Okta users are derived from the username part of the email address (before
@). For example, a new user with the email address
firstname.lastname@example.org will have SwaggerHub username
Note that SwaggerHub allows only the following characters in usernames:
A..Z a..z 0..9 - . _
Please make sure the SSO email addresses of your users contain valid usernames. Users with unsupported email addresses will not be able to log in via SSO.
Starting from v. 1.18.2, if another user with the same username already exists in SwaggerHub, a number is appended at the end of the new username to make it unique. For example,
email@example.com will become
firstname.lastname@example.org will become
When users log in for the first time, their usernames and email addresses are populated based on the values of the
userPrincipalName fields, or, as of v. 1.18.2, based on the values of the fields specified by the Profile name and Email options.
Starting from v. 1.18.2, the usernames are normalized so that they contain only the characters
A..Z a..z 0..9 - . _ and start and end with a letter or number. Duplicate usernames get a number at the end, for example,
j.smith3 and so on.
Currently, SwaggerHub does not support single logout (SLO). When users log out of the identity provider, they remain logged in to SwaggerHub and need to log out from SwaggerHub separately.
Any SSO users that exist in SwaggerHub (the ones that logged in to SwaggerHub at least once) count toward the license user limit.
In versions prior to 1.20.1, the internal users that were not migrated to SSO become inactive and do not consume the license. These users will not be able to log in to SwaggerHub. If you switch from SSO back to internal authentication, the internal users will become active again.
Note that SwaggerHub does not automatically remove users who were removed from your SSO provider, so, you need to delete them manually. These users remain in SwaggerHub along with active users and consume the license.
Delete SSO users
Introduced in SwaggerHub On-Premise 1.18.4.
An administrator can delete registered users from SwaggerHub On-Premise to free up license seats for other users.