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

[Etienne Dysli Metref]

On 09.03.21 10:17, Alan Buxey wrote:
> there is prior art here - eg
> https://github.com/IdentityServer/IdentityServer3/blob/master/source/Core/Constants.cs#L438

These are just the standard claims from
https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims

> attribute names come through as snake_case from the JWT token in json.

Where is it specified that JWT claim names have to be snake_cased?

> also, as a case example: in the UK, the National Health Service (NHS)
> when migrating to SAML moved their CamelCase
> attributes to the lower case (often underscore separated) values
> 
> https://developer.nhs.uk/apis/spine-core/legacy_authorisation.html
> https://digital.nhs.uk/services/nhs-identity/guidance-for-developers/detailed-guidance/scopes-and-claims

Please cite an actual specification instead of random examples of people
doing all sorts of things.

> there are probably considered reasons why certain things have been
> undertaken - e.g. JSON is case sensitive

Then cite those reasons and their backing arguments, so we can consider
them instead of just guessing.

  Etienne

-------------- 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/20210309/b4d8251a/attachment.asc>