> For the complete documentation index, see [llms.txt](https://docs.amitysolutions.com/ekoai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amitysolutions.com/ekoai/getting-started/eko/portal/sso-with-oidc.md).

# SSO with OIDC

Eko OpenID enables Single Sign On (SSO) with their Eko Account for a third party web application. The Eko user can access any third party web application integrated with Eko OpenID after signing in with their Eko account

## How Eko OpenID works

Eko OpenID authentication conforms to [OpenID Connect 1.0](http://openid.net/specs/openid-connect-core-1_0.html). The flow can be broken down into 4 steps including:

1. Redirect users to authenticate to Eko
2. Obtain authentication code from Eko
3. Request tokens using authentication code
4. Get user profile using access token (optional)

We're also providing Eko SSO with OpenID SDK for PHP and Javascript. You can download the SDK as the following link:

PHP: [SDK](https://github.com/EkoCommunications/EkoOAuthSDK-PHP)\
Javascript: [SDK](https://github.com/EkoCommunications/EkoOAuthSDK-Java)

If you're not using PHP or Javascript, we also provide SSO api in the topic:  

{% content-ref url="/pages/HDhpLCTlxv2VQvr3IAYb" %}
[Eko OpenID Flow](/ekoai/getting-started/eko/portal/eko-openid-flow.md)
{% endcontent-ref %}

## How to integrate with Eko OpenID

To integrate a third-party web application with Eko, it consists of these steps:

1. Register third party web application on Eko admin panel.
2. Use Eko OpenID SDK or Implement your own API.
3. Customize your web server configuration


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amitysolutions.com/ekoai/getting-started/eko/portal/sso-with-oidc.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.