Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(jans-cedarling): Use principal_identifier to map cedar-policy token entity ID #10615

Open
olehbozhok opened this issue Jan 14, 2025 · 1 comment
Open

chore(jans-cedarling): Use principal_identifier to map cedar-policy token entity ID #10615

olehbozhok opened this issue Jan 14, 2025 · 1 comment
Assignees
@olehbozhok
Labels
comp-jans-cedarling Touching folder /jans-cedarling enhancement kind-dependencies Pull requests that update a dependency file
Milestone
next-release

Comments

@olehbozhok
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In the current implementation, we create cedar-policy token entity IDs using a hard-coded field.
We should allow the user to specify how this ID is generated.

Describe the solution you'd like
in Trusted Issuer Metadata Schema we have specified principal_identifier for each token. If it is defined we should use value as field where ID of token entity is stored (Map to Cedar entity identifier).

Additional context
change in nativity plan link

chat link
@olehbozhok olehbozhok self-assigned this Jan 14, 2025
@mo-auto mo-auto added comp-jans-cedarling Touching folder /jans-cedarling kind-dependencies Pull requests that update a dependency file labels Jan 14, 2025
@olehbozhok
Copy link
Contributor Author

Better to do after merge #10549

@moabu moabu added this to the next-release milestone Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olehbozhok olehbozhok

Labels
comp-jans-cedarling Touching folder /jans-cedarling enhancement kind-dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
next-release
Development

No branches or pull requests
3 participants
@olehbozhok @moabu @mo-auto