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

PR for Issue #157 (Update CAEP & RISC Events and SSF Docs with txn claim) #180

Merged
merged 6 commits into from
Jun 11, 2024
Merged

PR for Issue #157 (Update CAEP & RISC Events and SSF Docs with txn claim) #180

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a0b1e88
Update openid-sharedsignals-framework-1_0.md
iamseanodentity Jun 6, 2024
3f5e84f
Update openid-sharedsignals-framework-1_0.md
iamseanodentity Jun 11, 2024
e5f5ccf
Update openid-sharedsignals-framework-1_0.md
iamseanodentity Jun 11, 2024
0a9790a
Update openid-sharedsignals-framework-1_0.md
iamseanodentity Jun 11, 2024
43a86d7
Update openid-sharedsignals-framework-1_0.md
iamseanodentity Jun 11, 2024
6e95dbe
Merge branch 'iamseanodentity-txn-and-clarifications' of https://gith…
iamseanodentity Jun 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions openid-sharedsignals-framework-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,12 @@ contributor:
org: Okta
email: [email protected]

-
ins: S. O'Dell
name: Sean O'Dell
org: The Walt Disney Company
email: [email protected]

normative:
CLIENTCRED:
author:
Expand Down Expand Up @@ -408,6 +414,7 @@ The following are hypothetical examples of SETs that conform to the Shared Signa
"iss": "https://idp.example.com/",
"jti": "756E69717565206964656E746966696572",
"iat": 1520364019,
"txn": 8675309,
"aud": "636C69656E745F6964",
"sub_id": {
"format": "email",
Expand All @@ -425,6 +432,7 @@ The following are hypothetical examples of SETs that conform to the Shared Signa
"iss": "https://idp.example.com/",
"jti": "756E69717565206964656E746966696572",
"iat": 1520364019,
"txn": 8675309,
"aud": "636C69656E745F6964",
"sub_id": {
"format": "complex",
Expand Down Expand Up @@ -456,6 +464,7 @@ The following are hypothetical examples of SETs that conform to the Shared Signa
"iss": "https://sp.example2.com/",
"jti": "756E69717565206964656E746966696572",
"iat": 1520364019,
"txn": 8675309,
"aud": "636C69656E745F6964",
"sub_id": {
"format": "email",
Expand All @@ -478,6 +487,7 @@ The following are hypothetical examples of SETs that conform to the Shared Signa
"iss": "https://myservice.example3.com/",
"jti": "756E69717565206964656E746966696534",
"iat": 15203800012,
"txn": 8675309,
"aud": "636C69656E745F6324",
"sub_id": {
"format": "catalog_item",
Expand Down Expand Up @@ -2029,6 +2039,7 @@ specific to the event type.
"iss": "https://idp.example.com/",
"jti": "756E69717565206964656E746966696572",
"iat": 1520364019,
"txn": 8675309,
"aud": "636C69656E745F6964",
"sub_id": {
"format": "phone",
Expand All @@ -2049,6 +2060,7 @@ specific to the event type.
"iss": "https://idp.example.com/",
"jti": "756E69717565206964656E746966696572",
"iat": 1520364019,
"txn": 8675309,
"aud": "636C69656E745F6964",
"sub_id": {
"format": "email",
Expand Down Expand Up @@ -2110,6 +2122,7 @@ multiple Receivers would lead to unintended data disclosure.
"iss": "https://transmitter.example.com",
"aud": ["receiver.example.com/web", "receiver.example.com/mobile"],
"iat": 1493856000,
"txn": 8675309,
"sub_id": {
"format": "opaque",
"id": "72e6991badb44e08a69672960053b342"
Expand All @@ -2123,6 +2136,9 @@ multiple Receivers would lead to unintended data disclosure.
~~~
{: title="Example: SET with array 'aud' claim" #figarrayaud}

### The "txn" claim {#txn-claim}
Transmitters SHOULD set the "txn" claim value in Security Event Tokens (SETs). If the value is present, it MUST be unique to the underlying event that caused the Transmitter to generate the Security Event Token (SET). The Transmitter, however, may use the same value in the "txn" claim across different Security Events Tokens (SETs), such as session revoked and credential change, to indicate that the SETs originated from the same underlying cause or reason.

### The "events" claim {#events-claim}
The "events" claim SHOULD contain only one event. Multiple event type URIs are
permitted only if they are alternative URIs defining the exact same event type.
Expand Down Expand Up @@ -2210,6 +2226,7 @@ The technology described in this specification was made available from contribut

-02

* added txn claims to non-normative SET examples and generic txn callout under SET Profile section RFC8417(#152)
* added spec version to metadata
* Added description as receiver supplied
* added language to make verification and updated events independent of events_supported
Expand Down
Loading