You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be a conflict between the SIOP Response format in the reference implementation and what's in the docs. The reference implementation payload includes a did property, whereas the payload format in the docs includes a sub_jwk property.
EDIT: I think I overlooked some things. The docs do include a did property, so just wondering if we should be including the sub_jwk.
The text was updated successfully, but these errors were encountered:
jdkizer9
changed the title
SIOP Response Format Conflict
SIOP Response Payload Conflict
Dec 11, 2020
As for why it's in OIDC, I believe it's because that framework doesn't have a PKI setup (hence DIDs in DID SIOP). It may be worth having this explicitly removed in DID SIOP, since there is a PKI built in. I could also be missing something though!
We have a did and sub_jwk property currently documented. Some of the details may change as DID-SIOP progresses through its next round of standardization. For the moment, I don't think we have anything to do on this issue, but please re-open if I'm missing something.
There appears to be a conflict between the SIOP Response format in the reference implementation and what's in the docs. The reference implementation payload includes a
did
property, whereas the payload format in the docs includes asub_jwk
property.EDIT: I think I overlooked some things. The docs do include a
did
property, so just wondering if we should be including thesub_jwk
.The text was updated successfully, but these errors were encountered: