Table of contents
1.
Introduction
2.
Single Sign-On (SSO)
3.
Advantages of SSO
4.
Configuring single sign-on
5.
Edit SSO settings
6.
Managing user accounts
7.
Creating end user accounts
8.
Adding existing user accounts
9.
Automatically adding new users
10.
Managing team logins
11.
Removing team access
12.
Next steps
13.
Logging in to an SSO team
14.
Frequently Asked Questions
14.1.
What kinds of requests can you make with Postman?
14.2.
What does Postman's endpoint mean?
14.3.
What is Postman ID?
14.4.
What does Postman's collection mean?
15.
Conclusion
Last Updated: Mar 27, 2024

Introduction to Single Sign-On (SSO) in postman

Author SHIVANGI MALL
0 upvote
Career growth poll
Do you think IIT Guwahati certified course can help you in your career?

Introduction

With numerous built-in tools that support each stage of the API lifecycle, the Postman testing tool offers a complete API development platform. With the Postman tool, you can create, mock, debug, run automated tests, document, monitor, and publish APIs all in one place. In this article, the reader will learn about Single Sign-On (SSO), the advantages of SSO, configuring single sign-on, and what are the steps involved in detail, and logging in to an SSO team.

Single Sign-On (SSO)

You can manage your team's identification across all of your SaaS applications by using single sign-on (SSO) services.

SSO services allow a user to log into various applications using just one set of credentials, such as their name or email address and password. The service removes additional prompts when a user switches applications while still in the same session and performs a single authentication of the end user for all applications to which they have access.

Google's implementation of sign-in for services like Gmail, YouTube, and Google Drive is an illustration of SSO. Any user who has an account with Google is immediately logged in to all of their other products.

Advantages of SSO

  • Users no longer need to keep and remember several passwords.
  • Allows customers to sign in at a single access point and enjoy a seamless experience across numerous applications, simplifying the user experience.
  • Reduces the number of support emails relating to passwords, increasing productivity.
  • Reduces phishing, preventing users from being duped into divulging critical information.

Configuring single sign-on

SSO for a Postman team can only be set up by a Team Admin.

  • To set up a new authentication technique:
  • Select Authentication under Team Settings.
  • To add an authentication method, select it.
  • Choose the type of authentication.
  • Enter a recognizable authentication name for your team.
  • Select Continue.

The Entity ID and the URLs for Login and ACS are pre-populated in the "Service Provider Details (Postman)" screen.

You must then complete the information in the Identity Provider Details section. In "X.509 Certificate," enter the authentication certificate issued by your identity provider.

You must log into your IDP account and fetch details in order to submit information in the Identity Provider Details area.

Edit SSO settings

You can choose the Status toggle to turn on or off SSO authentication for your Postman team after establishing it. This setting affects the entire team because it is a team-level option.
Select Edit to make changes to an authentication method's settings.

authentication 

Managing user accounts

The following subjects are covered in this section:

  • Making accounts for end users
  • Current user accounts are added
  • the automatic addition of new users
  • Managing team logins
  • taking away team access
  • Next actions

Creating end user accounts

For a user, you can make an Identity Provider account (IdP).

If the team has seats available and the Automatically add new users checkbox was set during SSO configuration, a Postman account will be created for the new user the first time they log in through the IdP.

The user will automatically get access to team resources and be assigned a developer role by the team.

Adding existing user accounts

If one of the following conditions is true when a Postman user logs in using a team's IdP, the user will automatically be joined to the team:

  • The Automatically add new users checkbox in your setup is turned on, and the team has open slots.
  • The user has been invited by an admin to join the team.

Automatically adding new users

Users who have accounts in your SSO system can join your team automatically by logging in to Postman using SSO by checking the option labeled "Automatically add new users" in your SSO configuration. If this is enabled, users can join your team by going to the Enterprise sign-in page and joining in with SSO, whether or not they already have Postman accounts.

Managing team logins

For Postman Professional or Enterprise teams implementing SSO, Postman, by default, only supports Service Provider initiated logins. To log into Postman, your team must utilize the Enterprise login page. You can build and copy the RelayState from your Postman team settings and save it in your IDP setup if you need users to be able to sign in from your SSO portal. When logins are started from a source that Postman is not familiar with, this ensures an additional layer of protection.

Removing team access

To limit access to shared resources in Postman, users must be removed from your team. You will continue to have access to any shared data even if a user is removed from your team. In order to ensure that the team doesn't lose access to any unshared work, you can reassign their personal workspaces and the data included in them to an active team member.

Next steps

After setting up SSO for your team, you might be curious to know how your team will use it and how to proceed with SCIM provisioning. See Logging into an SSO team for more information about the user experience.

Logging in to an SSO team

When single sign-on (SSO) has been enabled for Postman by your Team Admin, you can log in to Postman using a defined Identity provider.

A login URL that was created during the SSO setting can be shared by your Team Admin. You will be automatically redirected to the configured Identity Provider from the Login URL.

Signing up for Postman:

  • In Postman's upper-right corner, click Sign In.
  • In the upper-left, click Home, then click Sign in.
  • Select Sign In in the upper-right corner of Postman's website.

Your default browser will open a screen inviting you to sign in to Postman when you choose to sign into the Postman desktop application.

Once you begin the registration procedure from Postman, you have five minutes to complete it. If you stay longer than this, you must go back to Postman and sign in again.

Select Sign in with SSO to sign into Postman.

Sign In

To continue, enter the team domain.

Select If you want to continue to be signed in for 30 days after your current session ends before re-authenticating, stay signed in. Clear this checkbox if you don't want to stay logged in on the computer you are using. Keep in mind that after 30 minutes, you will be required to check in once again.
 

Sign in with Single Sign-On (SSO)

 

You will be forwarded to the configured SSO provider by Postman. To sign in, enter your SSO credentials.

You might need to take additional steps the first time you sign in to Postman to enable access to your identity provider account. Use SSO to log in, then follow your provider's instructions to link the account to Postman.

You will receive a confirmation on your browser after logging in, and your browser will then redirect you back to Postman.

You're signed in

You must sign in to each team separately if you are a member of numerous Postman teams with various authentication procedures. In order to do this, choose your avatar in the top-right corner, then choose the team.

Frequently Asked Questions

What kinds of requests can you make with Postman?

Request Method, Request URL, Request Headers, Request Body, Pre-request Script, and Tests are all included in an HTTP request method.

What does Postman's endpoint mean?

You may include Postman in your development toolchain by integrating it with the Postman API endpoints. Through the API, you can add and run monitors, update environments, add and run new collections, and update existing collections. You can now access data kept in your Postman account programmatically.

What is Postman ID?

Using their distinct id, individual resources in your Postman Account can be accessed ( uid ). The user-id and resource-id of the resource owner are simply concatenated to form the uid.

What does Postman's collection mean?

A collection of saved requests is called a Postman Collection. Every request you make in Postman is recorded in the sidebar's History tab.

Conclusion

 We hope this article helps you to learn something new. And if you're interested in learning more, see our posts on Introduction to PostmanLearn APIs (making APIs and JWT authentication), and Postman for API testing.

Visit our practice platform Coding Ninjas Studio to practice top problems, attempt mock tests, read interview experiences, and much more.! Feel free to upvote and share this article if it has been helpful for you.

 

Live masterclass