> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/news/2025/oidc-sso-supported.md).

# OpenID Connect (OIDC) SSO is now supported

In addition to SAML 2.0, Daxium-Air now supports Single Sign-On via OpenID Connect (OIDC).

**Published on February 10, 2025**

In addition to SAML 2.0 support, we're pleased to announce that Single Sign-On (SSO) authentication via **OpenID Connect (OIDC)** is now supported in Daxium-Air.

## OIDC vs SAML 2.0: what's the difference?

Both protocols enable secure, password-free access through SSO, but they address different needs:

* **SAML 2.0** — ideal for large enterprises with traditional applications (intranets, business tools). It relies on XML exchanges and fits perfectly in environments already equipped with an Identity Provider (IdP) such as ADFS or PingFederate.
* **OIDC (OpenID Connect)** — a more modern and flexible solution, particularly suited to web and mobile applications. Based on OAuth 2.0, it offers a lighter, standardized mechanism using JSON tokens (JWT), making it easier to integrate with identity providers such as Azure AD, Okta, Google, Auth0, Keycloak, and others.

With this new option, you can now choose between SAML 2.0 and OIDC to meet your SSO requirements.

{% hint style="info" %}
If your organization uses an OIDC-compatible Identity Provider, contact us to configure this authentication together in just a few steps. See the [Subscriptions, Licencing, SSO](https://www.center.daxium-air.com/user-documentation/build/building-the-platform/managing-users/subscriptions-licencing-sso) documentation for more information.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.center.daxium-air.com/news/2025/oidc-sso-supported.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
