- Introduction
- Installation and updates
- Sending your first request
- Navigating Postman
- New button
- Creating the first collection
- Postman account
- Syncing
- Settings
- Keyboard Shortcuts
- Troubleshooting In-app Issues
- Requests
- Authorizing requests
- Working with Tabs
- Responses
- Visualize API responses
- History
- Cookies
- Certificates
- Validating Requests Against Schema
- Generate code snippets
- Using GraphQL
- Making SOAP requests
- Capturing HTTP requests
- Proxy
- Interceptor
- Debugging and logs
- Troubleshooting API requests
- Intro to collections
- Creating collections
- Sharing collections
- Commenting on collections
- Managing collections
- Version Control for Collections
- Using Markdown for descriptions
- Examples
- Data formats
- Working with OpenAPI
- Collaborating in Postman
- Roles and permissions
- Managing your team
- Requesting access
- Team Settings
- Audit logs
- Intro to scripts
- Pre-request scripts
- Test scripts
- Test examples
- Branching and looping
- Postman Sandbox API reference
- Intro to collection runs
- Starting a collection run
- Using environments in collection runs
- Building workflows
- Running multiple iterations
- Sharing collection runs
- Working with data files
- Debugging a collection run
- Command line integration with Newman
- Integration with Jenkins
- Integration with Travis CI
- Newman with Docker
- Documenting your API
- Authoring your documentation
- Publishing your docs
- Viewing documentation
- Custom documentation domains
- Intro to mock servers
- Setting up a mock server
- Mocking with examples
- Mocking with the Postman API
- Matching algorithm
- Intro to Monitoring
- Setting up a monitor
- Viewing monitor results
- Monitoring APIs and websites
- Set up integrations to receive alerts
- Running Postman monitors using static IPs
- Troubleshooting monitors
- FAQs for monitors
- Intro to Workspaces
- Creating Workspaces
- Using Workspaces
- Managing Workspaces
- Viewing changelogs and restoring collections
- Conflicts
- The API Workflow
- Managing and Sharing APIs
- Versioning APIs
- Viewing and analyzing APIs
- Validating Elements Against Schema
- Customizing Postman
- Notifications
- Find and Replace
- Purchasing Postman
- Billing
- Intro to SSO
- Configuring SSO for a team
- Logging in to an SSO team
- Configuring Microsoft AD FS with Postman SSO
- Setting a custom SAML in Azure AD
- Setting up custom SAML in Duo
- Setting up custom SAML in GSuite
- Setting up custom SAML in Okta
- Setting up custom SAML in Onelogin
- Setting up custom SAML in Ping Identity
- Intro to Integrations
- Custom Webhooks
- APIMatic
- BigPanda
- Coralogix
- Datadog
- Dropbox
- GitHub
- GitLab
- HipChat
- Keen
- Microsoft Flow
- Microsoft Teams
- PagerDuty
- Slack
- VictorOps
Intro to SSO
What is SSO?
Single Sign-On (SSO) services make it easy to manage your team’s identity across all the SaaS products that you use.
SSO services permit a user to use one set of login credentials (e.g., name/email and password) to access multiple applications. The service authenticates the end user only 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 implementation of login for their products, such as Gmail, YouTube, and so on. Any user that is logged in to one of Google's products is automatically logged in to their other products as well.
What are the advantages of SSO?
- Removes the need for users to remember and manage multiple passwords.
- Simplifies users' experience by allowing them to log in at one single access point and enjoy a seamless experience across multiple applications.
- Increases productivity by significantly reducing the password-related support emails.
- Reduces phishing and thereby making sure users aren't tricked into giving away sensitive information.
Prerequisites for SSO with Postman
- Team’s Identity Provider (IdP) must support the SAML 2.0 standard.
Identity Providers Supported
SSO setup for SAML 2.0 compliant IdPs
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 after configuring SSO in the Edit Team Page.
Learn more about setting up SSO.
Note: While configuring your IdP, make sure the user’s email address is set in attribute statements.
Note: Postman’s form-based authentication mechanism and Google OAuth 2.0 remain enabled even if SSO is configured for a team.