[Openid-specs-ab] claims format guidance
Davide Vaghetti
davide.vaghetti at garr.it
Tue Mar 9 12:17:31 UTC 2021
Hello everyone,
in the OIDF Research and Education WG we are currently discussing about
how to translate legacy LDAP schemas widely used by our community into
OIDC claims.
The main schemas we are dealing with are eduperson [1] and schac [2].
The attributes in the schemas are specified in camelCase format and that
naming has also became the standard for the use with SAML 2.0.
Coming to OIDC, it seems that the most widely used naming convention is
based on snake_case, which has also been employed in an early effort to
port the above schemas to OIDC [3].
Currently we are working on a specification that should provide an
official translation and there is some discussion about keeping the
snake_case format or revert that decision and use instead the original
camelCase one.
Obviously, before taking any decision we will consider the current
implementations and what format they use, but to help in the decision
process I wonder if are there some specific guidelines or policy about
the naming convention for new claims?
Thanks,
Davide
[1] https://wiki.refeds.org/display/STAN/eduPerson
[2] https://wiki.refeds.org/display/STAN/SCHAC+Releases
[3]
https://wiki.refeds.org/download/attachments/38895621/20181011-OIDC-WP.pdf
--
Davide Vaghetti
Consortium GARR
Tel: +390502213158
Mobile: +393357779542
Skype: daserzw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4428 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20210309/63fbcb79/attachment.p7s>
More information about the Openid-specs-ab
mailing list