Registration - 2.1 jwk_encryption_url def wrong

[Nat Sakimura]

jwk_encryption_url mentions that it is used for signing of token endpoint, but it is for encryption.

Also, signing or encrypting an endpoint does not make sense. It needs to be either the request or response.

[Edmund Jay]

The current definition is wrong.

OPTIONAL. URL for the Client's JSON Web Key [JWK], used for JWE [JWE] encryption of Token Endpoint Response. 

The Token Endpoint currently does not return encrypted responses. I think it should be written more like the x509_encryption_url definition :

OPTIONAL. URL for the Client's JSON Web Key [JWK], used for JWE [JWE] encryption of JWT [JWT] to the Client. If the client registers both jwk_encryption_url and x509_encryption_url the keys contained in both formats SHOULD be the same. 

[John Bradley]

Changed encryption of Token Endpoint Response. to encryption of ID Token and User Info Endpoint Responses to the Client. for another ticket. will add missing text about keys matching.

[John Bradley]

re #472 add text about jwk and x5u keys matching

→ 5a202ac2a4d5

[Michael Jones]

John has already fixed this as part of another ticket