Single Sign-On (SSO) Integration Made Easy
Make authentication effortless for your users. With Single Sign-On (SSO) in API Maker, people can log in using identity providers such as Google, Azure AD, and AWS, while your APIs remain secure and governed by the rules you define.
No duplicate accounts. No password fatigue. Just smooth, secure access backed by modern authentication standards.
Why Choose SSO with API Maker
Authentication should feel invisible, not like a hurdle. With Single Sign-On in API Maker, your users log in once and get secure access to everything they need.
One login, many APIs: No more switching accounts or managing extra passwords. A single sign-in with Google, Azure AD, or AWS gives users access across all your protected APIs.
Security you can rely on: Tokens are verified directly with the identity provider, then matched against your rules in API Maker. You stay in control of who sees what, while keeping enterprise-grade security.
Onboarding made simple: New users don’t have to create yet another account. They can get started right away with the credentials they already use every day.
Flexibility for every use case: Protect some APIs with SSO and others with service tokens. Combine methods to fit the way your product and teams actually work.
Grows with your business: Whether you are running a small project or serving thousands of users, SSO scales effortlessly with your needs.
How It Works
Here’s what happens when a user makes a request with SSO enabled:
The user signs in
Instead of creating a new password, they log in with a provider they already trust, like Google, Azure AD, or AWS.The provider issues a token
A secure, short-lived token is generated to confirm their identity.The token travels with the request
Your application includes this token in the request header when calling an API Maker endpoint.API Maker takes care of the rest
The token is verified, the user is mapped to groups or roles you have defined, permissions are applied, and the request is executed.
Visual Flow Of SSO
- The user signs in once using Google, Azure AD, or AWS. From there, a single authorization grants seamless access to multiple systems such as employee portals, CRM systems, or custom business apps.
Key Highlights
Works with JWT-based identity providers: Google, Azure AD, AWS.
Simple header-based auth for secure API calls.
Fine-grained access by mapping identity provider roles to API Maker groups.
Secure credential storage in API Maker’s Default Secret.
Compatible with API Maker tokens for hybrid setups.
Real-World Benefits
For developers: Save time and effort, no need to build or maintain custom OAuth servers.
For teams: Employees use their existing corporate logins to access internal APIs without friction.
For enterprises: Automatically map provider roles (e.g., Admin, Manager, Viewer) to API Maker permissions.
For customers: Deliver a familiar and trusted login experience that improves adoption.
Best Fit Use Cases
SaaS platforms offering enterprise logins via Azure AD or Google Workspace.
Internal applications that align with company-wide Google or Azure accounts.
APIs that require hybrid authentication, mixing end-user SSO with machine-level tokens.
FAQs
Which providers are supported?
Google, Azure Active Directory, and AWS.
Do I need to install third-party packages?
No. API Maker natively validates tokens once configured.
Can I mix SSO with API Maker tokens?
Yes. Use SSO for end-users and API Maker tokens for machine-to-machine access, or assign them to different endpoints.
What happens if a token expires?
Users simply reauthenticate with the identity provider, which issues a new token. API Maker always enforces validity.
Where are provider credentials stored?
In the Default Secret section of API Maker, keeping them secure and separate from your code.
Enable Single Sign-On (SSO) in API Maker with Google, Azure AD, and AWS. Provide secure, frictionless authentication for your users, map identity provider roles to API Maker permissions, and protect APIs without building custom authentication infrastructure.
