Single sign-on for your account now takes SAML 2.0, next to OpenID Connect, Google and GitHub. If your company signs in through ADFS, PingFederate, OneLogin, JumpCloud, or a SAML app in Okta, Microsoft Entra ID or Google Workspace, your members can use it to sign in to ngris. It comes with single sign-on, on the same plans.
What's new
- SAML as a provider type. Add it under Account → Single Sign-On. Give your IdP's metadata by URL (ngris reads it again regularly, so new certificates are picked up by themselves) or pasted.
- Each setup has its own values for your IdP: the ACS URL, the entity ID and ngris's metadata URL, on the Single Sign-On page with Copy buttons.
- A start URL for your IdP's app tile. Every sign-in starts at ngris: the tile opens a page where the member clicks Continue.
- Members are linked to their IdP identity at their first SAML sign-in. Admins see the linked members on the Single Sign-On page and can reset a link, confirmed with their password.
- Changing the IdP is confirmed by a person. Another IdP, another metadata URL or a certificate you paste needs your password and a new DNS record, like any provider change.
- Test reads your IdP's metadata again and shows when its signing certificates end.
Get started
- Under Account → Single Sign-On, add a provider, choose SAML, enter your email domain and save.
- Copy the setup's ACS URL and entity ID into a SAML app in your IdP. Set the Name ID format to Persistent and send the member's email.
- Give ngris your IdP's metadata, verify your domain, then use Test.
- Read the docs: SAML single sign-on.