[openid-specs-rande] SAML to OIDC mapping specification

[Etienne Dysli Metref]

On 03.03.21 20:05, Marcus Hardt wrote:
> I am not aware of different implementations. Are there any that did it
> differently?

Perhaps our peers in Australia? AAF has an OIDC service since 2018 [1],
but their OP's discovery [2] doesn't list claims_supported, so I can't tell.

Our SWITCH edu-ID OIDC OP use the same camelCase claim names as its SAML
part.

>> On 02.03.21 12:28, Marcus Hardt wrote:
>>> Unless there is a very good reason to drop the '_', I don't think
>>> this will happen.

My reasoning is that renaming claims while keeping their meaning and
values identical to SAML attributes introduces unnecessary complexity.
This kind of complexity can confuse deployers. Moreover, it was based on
a misunderstanding of the OIDC specification.

Let's face it: no reason will be good enough to make people change if
they don't want to. ;P

Davide, I propose that the working group votes on camelCase versus
snake_case claim names format to settle the question. Then we can move on.

Cheers,
  Etienne

[1]
https://support.aaf.edu.au/support/solutions/articles/19000096640-openid-connect-
[2] https://central.aaf.edu.au/.well-known/openid-configuration

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openid.net/pipermail/openid-specs-rande/attachments/20210308/2227ae17/attachment.asc>