Standard 5.3 - Define minimum registration contents for requests to self-issued OPs

Issue #739 resolved
Michael Jones created an issue

We don't currently say what these are. Messages contained this example, but I'm deleting it because it makes no sense when also specifying a "userinfo" section.

"registration": { "redirect_uris": "https://rp.com/authz/callback", "logo_url": "https://rp.com/logo.png", "jwk_url": "https://rp.com/public_key.jwks", "id_token_encrypted_response_alg": "RSA1_5", "id_token_encrypted_response_enc": "A128CBC+HS256" }

Comments (5)

  1. Michael Jones reporter

    I'd like you to take a stab at this, John. It's fine if you just want to add the information to the bug and have me do the actual edits. Thanks.

  2. John Bradley

    On second thought they are all optional.

    I worded the one for redirect_uris to default to the redirect_uri.

    If this is unsigned sending the redirect_uri twice so that you can compare them is silly given that we are trying to keep the request size down.

    I used jwk_encryption_url rather than jwk_url as it is only used to encrypt to the client.

    The claims are redirect_uris jwk_encryption_url id_token_encrypted_response_alg id_token_encrypted_response_enc policy_url tos_url logo_url

  3. Log in to comment