CIBA: login_hint_token_signing_algorithms_supported

[Dave Tonge]

From FAPI:

Why is there no registration metadata value for login_hint_token_signing_algorithms_supported

[Takahiko Kawasaki]

Unless I'm missing something, CIBA Core does not mention anything about the format of the value of login_hint_token. My understanding is that details of the format will be described in each profile or be left to each authorization server implementation. CIBA Core does not say that the format is JWT (does it?), so the metadata is not appropriate. However, it is up to FAPI-CIBA profile whether it states the format of login_hint_token MUST be JWT and adds the metadata under the name of FAPI-CIBA profile.

[Dave Tonge]

Yep I agree and propose we close this issue.

[Brian Campbell]

I also agree and think we should close this issue.

[Brian Campbell]

For reasons previously mentioned and the general consensus on the Jan 8th 2019 call http://lists.openid.net/pipermail/openid-specs-mobile-profile/Week-of-Mon-20190107/001408.html was to close this.