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.

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

Event Subject Claim #2

Open
dickhardt opened this issue Dec 1, 2017 · 0 comments
Open

Event Subject Claim #2

dickhardt opened this issue Dec 1, 2017 · 0 comments

Comments

@dickhardt
Copy link

dickhardt commented Dec 1, 2017

Do we specify how a subject is included in a SET or let profiles define that?

The current draft draft-ietf-secevent-token-03 defines the sub claim as an optional string or URI, with semantics left to the profile. This claim is placed in the SET envelope. No "subject" claim is defined inside the event object, which means that profiles are free to define such claims as they see fit.

Alternatively, we could have an event_subject claim inside the event object, with a "SHOULD" normative status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant