Thanks Eve. I was a young identity technical architect in the mid 2000’s working deeply in SAML2 for NZ government. Then in the 2010’s when OAuth2/OIDC came along it felt in many ways like OAuth2/OIDC was “SAML for JSON” so I liked your comment on the “double-redirect pattern … that looked awfully similar to SAML”.
As we know, OIDC is being used as a base standard for advancing new areas of identity : VCs. I’m quite interested how earlier standards can act as transport layers to the ever-advancing new standards. So, simplistically we have |SAML| -- (JSON) --> |OIDC| --(VCs) --> |OIDC2VC|
In some ways standards are like music. Always being influenced from past styles while at the same time always trying to invent a “new (sick) beat”.
Thanks Eve. I was a young identity technical architect in the mid 2000’s working deeply in SAML2 for NZ government. Then in the 2010’s when OAuth2/OIDC came along it felt in many ways like OAuth2/OIDC was “SAML for JSON” so I liked your comment on the “double-redirect pattern … that looked awfully similar to SAML”.
As we know, OIDC is being used as a base standard for advancing new areas of identity : VCs. I’m quite interested how earlier standards can act as transport layers to the ever-advancing new standards. So, simplistically we have |SAML| -- (JSON) --> |OIDC| --(VCs) --> |OIDC2VC|
In some ways standards are like music. Always being influenced from past styles while at the same time always trying to invent a “new (sick) beat”.
Thanks for the comment, Richard! Indeed, this stack is proving to be quite “generative” in supporting new innovation.