What it does
Not available. KynetraDB has no SAML and no OpenID Connect single sign-on in this release. Sign-in is by password, one-time code, or Google and GitHub OAuth.
How it works
Three things in the engine can look like single sign-on and are not. An organisation's security policy has a status field for single sign-on and a list of JWKS endpoint URLs; both are stored as configuration metadata, nothing reads the URLs, and they do not affect authentication. A library module in the server crate verifies RS256 tokens from an external issuer, but no route or middleware calls it. A plugin crate defines SAML and OAuth-introspection extension points, and nothing in the server loads a plugin.
If your deployment needs SAML or OpenID Connect today, use password, one-time-code or OAuth sign-in, or manage identity in your own service and call KynetraDB from a server you control with a project service key.
Limits
- SAML single sign-on is not available.
- OpenID Connect providers other than Google and GitHub are not available.
- The JWKS endpoint list on an organisation policy has no effect on authentication.
Evidence
- On this siteAvailable now: Google and GitHub OAuth
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.