[codex] Remove invalid OIDC scopes from example integration#126
Merged
[codex] Remove invalid OIDC scopes from example integration#126
Conversation
Deploying qf-api-docs with
|
| Latest commit: |
939bf26
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7942fc80.qf-api-docs.pages.dev |
| Branch Preview URL: | https://codex-fix-example-integratio.qf-api-docs.pages.dev |
basit3407
force-pushed
the
codex/fix-example-integration-oidc-scopes
branch
from
ec72aeb to
939bf26
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The web integration example was implying separate OIDC profile and email scopes. In this setup, the docs and implementation use openid, offline_access, and API scopes such as �ookmark, collection, and user instead.
Validation