Map identity public metadata to id_token in AX consent
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 96
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe your problem
The Ory Account Experience does not map any Identity public metadata to the id_token. It only maps the Identity traits. As a user I want to specify data inside he public metadata and have it populate based on the scopes provided.
Describe your ideal solution
Map the public metadata to the id_token when the scope contains the key.
Workarounds or alternatives
A custom consent UI can also be implemented, but this requires a lot of work for only a couple more fields in the id_token!
Version
latest
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; start by locating the Ory Account Experience consent flow and its id_token claim mapping. Determine how scopes authorize public metadata claims, and consider the work complete when scoped public metadata is reflected in the id_token.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100