Bodhaka LumenIntegration guides › Other single sign-on (OpenID Connect or SAML 2.0)
Integration guide
Other single sign-on (OpenID Connect or SAML 2.0)
Connects any identity provider that supports OpenID Connect or SAML 2.0, so people sign in to Bodhaka Lumen with their organisation’s account.
What you need
- An identity provider that supports OpenID Connect or SAML 2.0.
- An administrator of that provider.
Permissions requested and why
| Permission or scope | What it allows | Why it is needed |
|---|---|---|
openid | Sign in | Proving who the person is. |
email | Read the email address | Matching the person to their account. |
profile | Read the name | Showing the person’s name once they are in. |
SAML attributes | Email address and name | For SAML, the same two facts are read from the assertion. Nothing else is requested. |
Bodhaka Lumen asks for nothing beyond this list. Credentials you enter are encrypted with your workspace’s own key and are never shown again after saving.
How to connect
- In Bodhaka Lumen, open Integrations, choose OpenID Connect or SAML 2.0, and copy the redirect address or service provider details shown.
- At your identity provider, create the application with those details.
- Enter the provider’s issuer address, client ID and secret (OpenID Connect) or its metadata (SAML) in Bodhaka Lumen.
- Try the connection, then switch it on.
How to disconnect and delete data
- Remove the integration in Bodhaka Lumen. Stored secrets are deleted and the sign-in button disappears.
- Delete or deactivate the application at your identity provider.
To have any data that came through this integration deleted from Bodhaka Lumen, your workspace administrator can delete it, or write to support@bodhakalumen.com. See the Privacy Policy.
Want early access?
Tell us about your school or organisation and we will be in touch.