Single sign-on (SSO) services enable you to manage your team's identity across all the SaaS products that you use.
With an SSO service, a user can access multiple applications using one set of credentials (for example, an email address and password). The SSO service authenticates the user once for all the applications the user has been given rights to and eliminates further prompts when the user switches applications during the same session.
An example of SSO is Google's sign-in implementation for products like Gmail, YouTube, and Google Drive. Any user who is signed in to one of Google's products is automatically signed in to their other products as well.
Most SAML 2.0 compliant identity providers require the same information about the service provider for setup (Postman is the service provider). These values are specific to a Postman team and are available while configuring SSO.
While configuring your IdP, make sure to set your users' email address in SAML attributes and claims. Postman expects to receive an email address from your IdP to identify each user.
If you configure SSO, Postman Password and Google OAuth 2.0 authentication methods remain enabled for your team. You can turn off these authentication methods to only allow your team to sign in using SSO.
To learn more about SSO and SCIM, see the following:
Last modified: 2024/10/03
Additional resources
Videos
Case Studies