[Openid-specs-ab] Issue #1573: Static metadata for the authz server (openid/connect)

[David Chadwick]

New issue 1573: Static metadata for the authz server
https://bitbucket.org/openid/connect/issues/1573/static-metadata-for-the-authz-server

David Chadwick:

Currently there is no simple way for the RP to determine the endpoint of the authorization server that is protecting the wallet when the same device flow is used in OIDC4VPs \(and when SIOPv2 is not being used. When SIOPv2 is being used the meta data has been defined\). It is proposed that we define the static metadata for the authorization server analagous to the way that Static Self-Issued OpenID Provider Discovery Metadata has been defined in the SIOPv2 spec.

It is proposed that the static metadata might look something like this

\{  
"authorization\_endpoint": "oidc4vps:",  
"response\_types\_supported": \[  
"vp\_token"  
\],  
"presentation\_definitions\_types\_supported": \[  
"presentation\_definition\_uri"  
\],  
"presentation\_submission\_locations\_supported": \[  
"separate\_response\_parameter"  
\],  
"vp\_formats\_supported": \[  
"jwt\_vp"  
\],  
"vc\_formats\_supported": \[  
"jwt\_vc"  
\],  
"vp\_signing\_alg\_values\_supported": \[  
"ES256"  
\],  
"vc\_signing\_alg\_values\_supported": \[  
"ES256"  
\]  
\}