Organizations
Single sign-on
Connect Okta, Entra ID or Google Workspace over SAML 2.0 or OpenID Connect, and require it for your domains.
Built Your people sign in to OpenPulse through the identity provider you already run, over OpenID Connect or SAML 2.0. An organization connects one provider. The owner or an admin sets it up in the Console under Sign-in rules → Single sign-on.
Set it up#
Verify your email domain
Add the domain in the Console, publish the TXT record it shows at your DNS and press Check DNS. A domain belongs to one organization, and your provider speaks only for your verified domains.Connect the provider
Choose SAML 2.0 or OpenID Connect and follow the values for your provider below.Sign in once yourself
Confirm that the connection works before anyone depends on it.Require it
Press Require single sign-on. This needs at least one verified domain.
Okta over SAML 2.0#
In Okta, open Applications → Create App Integration → SAML 2.0 and enter the values the Console shows:
| Okta field | Value |
|---|---|
| Single sign-on URL | https://openpulse.org/auth/saml/acs/<org> |
| Audience URI (SP Entity ID) | https://openpulse.org/auth/saml/metadata/<org> |
| Name ID format | EmailAddress |
| Application username | Email |
| Response and Assertion Signature | Signed |
A fixed name ID also works (user.id, format Unspecified) with an attribute statement named email set to user.email. Assign the app to the people or groups who should sign in. Then open Sign On → SAML Signing Certificates → Actions → View IdP metadata and copy that URL into the Console as the provider metadata URL.
The tile in the Okta dashboard works. OpenPulse accepts only answers to a request it sent, so the tile sends the browser through the OpenPulse sign-in start and Okta answers that request.
Okta over OpenID Connect#
In Okta, open Applications → Create App Integration → OIDC, Web Application. Set the sign-in redirect URI to https://openpulse.org/auth/sso/callback and the grant type to Authorization Code. OpenPulse requests the scopes openid email profile. In the Console, enter the issuer, the client ID and the client secret.
Entra ID#
| Protocol | Setup |
|---|---|
| SAML 2.0 | Create an Enterprise application with SAML. The Identifier is the entity ID, the Reply URL is the assertion consumer URL, and the Console takes the App Federation Metadata URL. The email is read from the emailaddress claim. |
| OpenID Connect | Use your own tenant's issuer, https://login.microsoftonline.com/<tenant id>/v2.0. Multi-tenant endpoints are refused, because any tenant could then speak for your domain. Add the optional ID token claims email and xms_edov. |
Google Workspace#
Add a custom SAML app with the same two values, set the name ID to Basic Information > Primary email, and paste the metadata file Google gives you into the Console. Google publishes no metadata URL, so paste the new file when its certificate changes.
What requiring it covers#
An email link for an address on your verified domains is refused and the person is sent to your provider. A passkey or a device that is already signed in keeps working until its session ends. To end those sessions, use Sessions.
What each sign-in checks#
| Check | What OpenPulse verifies |
|---|---|
| SAML | The signature under your certificates, issuer, audience, recipient and validity, and that the assertion answers a request sent in the last ten minutes. Each request answers once and each assertion is accepted once. |
| OpenID Connect | The signature under the provider’s JWKS, issuer, audience, expiry, nonce and PKCE, and a token minted in the last ten minutes. The email must be vouched for by the provider. |
| Domain | The email is at a verified domain of this organization. |
| One account, one identity | The provider account named at a person’s first sign-in is pinned to their identity. If the provider later gives that email to another account, the sign-in is refused and recorded. An admin can release the pin in the Console for someone who really has a new account. |
Keys that rotate#
OpenID Connect keys are read from the provider's JWKS. SAML certificates are read again from the metadata URL when a signature stops verifying, so a rolled certificate needs no action unless you pasted a metadata file.
Not supported yet#
- Signed sign-in requests and encrypted assertions.
- Single logout from the provider. Deactivating someone through SCIM ends their sign-ins.
- Roles from assertion attributes. Groups come through SCIM.
- Accounts made at the first sign-in without an invitation.