- edited description
CIBA example needs updating
The example in https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0-03.html#rfc.section.7.1 has a login_hint_token that used the format from the Subject Identifiers draft (https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers-04 at the time). However, a change to the format was recently introduced in a new version of that draft https://mailarchive.ietf.org/arch/msg/id-event/D0F-o_RSA_X2wOeWi1upAqMnHY8/ (the `subject_type` member has been changed to `format`). The CIBA example should be updated accordingly.
Current snippet from the example:
login_hint_token=eyJraWQiOiJsdGFjZXNidyIsImFsZyI6IkVTMjU2In0.eyJ
zdWJfaWQiOnsic3ViamVjdF90eXBlIjoicGhvbmUiLCJwaG9uZSI6IisxMzMwMjg
xODAwNCJ9fQ.Kk8jcUbHjJAQkRSHyDuFQr3NMEOSJEZc85VfER74tX6J9CuUllr8
9WKUHUR7MA0-mWlptMRRhdgW1ZDt7g1uwQ
Decoded payload of the token:
{
"sub_id": {
"subject_type": "phone",
"phone": "+13302818004"
}
}
AFAICT it should be changed to:
{
"sub_id": {
"format": "phone",
"phone": "+13302818004"
}
}
Comments (7)
-
reporter -
reporter also in the signed request https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0-03.html#rfc.section.7.1.1 examples
-
-
assigned issue to
-
assigned issue to
-
reporter - edited description
-
- changed status to resolved
Update CIBA login_hint_token example to align with change in subject identifiers draft where
subject_type is now
format` fixing Issue#199→ <<cset b8ffd65d77f6>>
-
reporter also 1ebd376
-
Update CIBA login_hint_token example to align with change in subject identifiers draft where
subject_type is now
format` fixing Issue#199→ <<cset 245b712c1963>>
- Log in to comment