This page is for organization administrators. It describes how to configure Hypar authentication to use your company's login system. SAML and OIDC require an enterprise contract with Hypar.
Google Workspaces
No configuration needed. Instruct your users to click Continue with Google on the Hypar sign-in page.
SAML on Azure
You register Hypar as an SSO application on your side, then send the Hypar team the metadata URL.
Quick start
- Identifier (Entity ID):
urn:amazon:cognito:sp:us-west-2_zqP9PvduV
- Reply URL (Assertion Consumer Service URL):
https://auth.hypar.io/saml2/idpresponse
- Add a Group Claim for Groups assigned to the application, Source attribute = Group ID
Detailed steps
- Add the application. Azure Portal → Azure Active Directory → Enterprise applications → New application → Create your own application → name it "Hypar", select Integrate any other application you don't find in the gallery (Non-gallery) → Create.
- Configure SAML. On the app's page: Set up single sign-on → SAML. Edit Basic SAML Configuration: set the Identifier and Reply URL from Quick start above. Save.
- Add the group claim. Under User Attributes & Claims → Edit → Add a group claim → Groups assigned to the application, Source attribute Group ID. Save.
- Send us the metadata. Under SAML Signing Certificate, copy the App Federation Metadata Url and send it to your Hypar representative.
OIDC
Hypar supports OIDC authentication. Contact support@hypar.io to get set up.
Last verified against Hypar v0.2.019 (July 10, 2026).