Version Management Concept

[Torsten Lodderstedt]

If we will make a breaking change to the spec, we will need a concept for version management so RPs can detect what version the OP supports and act accordingly.

[Torsten Lodderstedt]

Proposal:

• OP announces supported schema versions in metadata (claims request parameter and verified_claims)
• RP specifies version of claims parameter payload (using metadata tag) and expected verified_claims version
• OP adds verified_claims version to JSON object (using metadata tag)

‌

[Torsten Lodderstedt]

I did a quick research how one could refer to the schema (version).

It seems there are several options:

Additional elements in the JSON payload

from https://tools.ietf.org/html/draft-handrews-json-schema-02#section-8.2.4.

{
  "$ref": "http://openid.net/schemas/verified_claims_request-09.json",
  "userinfo": {
    "verified_claims": {
      "verification": {
        "trust_framework": {
          "value": "jp_aml"
        },
        "time": null,
      },
      "claims": {
        "given_name": null
      }
    }
  }
}

Link Header

https://tools.ietf.org/html/draft-handrews-json-schema-02#section-11

Link: <https://example.com/my-hyper-schema#>; rel="describedby"

Accept/Content Header

https://tools.ietf.org/html/draft-handrews-json-schema-02#section-11

Accept: application/json;
          schema="https://example.com/qiang https://example.com/li",
        application/json;
          schema="https://example.com/kumar"

Content-Type: application/json;
          schema="https://example.com/my-hyper-schema#"

‌

‌

[Mark Haine]

Wontfix agreed by Torsten