Skip to content

SSO - Allow self signed identity server #1471

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 19, 2025
Merged

SSO - Allow self signed identity server #1471

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
581dd9f
sso docs
imilinovic Nov 19, 2025
44fd182
Update pages/database-management/authentication-and-authorization/aut…
matea16 Nov 19, 2025
e9c6e8f
Merge branch 'memgraph-3-7' into sso-docs
matea16 Nov 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions ...tabase-management/authentication-and-authorization/auth-system-integrations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -470,6 +470,18 @@ You can determine token audiences by decoding tokens via tools like `jwt.io` and
inspecting the `aud` field. In many cases, both tokens use the same audience
(for example, Entra ID uses the client ID).

{<h5 className="custom-header">Self-signed certificates</h5>}

If your custom OIDC identity provider uses self-signed certificates, you can
configure Memgraph to trust them by setting the `MEMGRAPH_SSO_CUSTOM_OIDC_EXTRA_CA_CERTS`
environment variable. This variable should point to a file containing the CA
certificates that should be trusted when connecting to your
identity server.

```bash
MEMGRAPH_SSO_CUSTOM_OIDC_EXTRA_CA_CERTS=/path/to/ca-certificates
```

#### Connect via Neo4j drivers

When connecting through a Neo4j driver, you can provide:
Expand Down