Map identity public metadata to id_token in AX consent

Benehiko commented 1 year ago

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[X] 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

aeneasr commented 1 year ago

I believe we have an item on the backlog to allow customizing the session data using a JsonNet which receives the request context + identity information, which would solve this issue too. It's however currently not on the roadmap iirc.

github-actions[bot] commented 1 month ago

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

open a PR referencing and resolving the issue;
leave a comment on it and discuss ideas on how you could contribute towards resolving it;
leave a comment and describe in detail why this issue is critical for your use case;
open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

ory / network