# How do I set up Adaptive content with my custom OIDC provider?

Adaptive content works with any identity provider

#### **Using OIDC Integration**

1. Set up the Generic OIDC integration in GitBook
2. Configure your OIDC provider to include custom claims in tokens
3. Map these claims in your GitBook visitor schema
4. The specific claim format depends on your provider's implementation

#### **Common Issues:**

* **Claim scopes:** Ensure your OIDC provider includes custom claims in the token (not just standard OIDC claims)
* **Claim structure:** Custom claims may be nested under provider-specific properties
* **Token validation:** Verify your provider's tokens are properly formatted
* **Provider-Specific Notes:** Different OIDC providers structure custom claims differently. Check your provider's documentation for how to include custom claims in ID tokens.


---

# Agent Instructions: 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:

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/published-documentation/adaptive-content/how-do-i-set-up-adaptive-content-with-my-custom-oidc-provider.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.