[WG-UMA] Issue 19: JRD for AM metadata

1 view
Skip to first unread message

Eve Maler

unread,
Feb 1, 2012, 6:29:15 PM2/1/12
to WG UMA
Regarding issue #19...

https://github.com/xmlgrrl/UMA-Specifications/issues/19

...seeing Axel Nennker's recent blog post advertising the various test server endpoints for the ongoing OpenID Connect interop activity...

http://ignisvulpis.blogspot.com/2012/01/openid-connect-test-servers.html

...I was struck by how easy it was to convey the relevant config/metadata information. Though "JRD" doesn't seem viable as a choice that's a direct alternative to XRD these days, I thought maybe we could just follow OpenID Connect's lead for our own AM metadata. Here's what it could look like.

AM location initially supplied: example.com

Derived UMA configuration location:

https://example.com/.well-known/uma-configuration

Sample UMA configuration data found at location:

{
"version":"1.0",
"issuer":"https://www.example.com",
"dynamic_client_registration_supported":"yes",
"token_types_supported":[
"artifact"
],
"host_grant_types_supported":[
"authorization_code",
"client_credentials"
],
"claim_types_supported":[
"openid"
],
"host_token_endpoint":"https://am.example.com/host/token_uri",
"host_user_endpoint":"https://am.example.com/host/user_uri",
"token_status_endpoint":"https://am.example.com/host/token_validation_uri",
"permission_registration_endpoint":"https://am.example.com/host/perm_reg_uri",
"requester_token_endpoint":"https://am.example.com/requester/token_uri",
"permission_request_endpoint":"https://am.example.com/requester/token_uri"
}

It is a lot shorter than our XRD format (for which see http://docs.kantarainitiative.org/uma/draft-uma-core.html#am-metadata-example) for several reasons: JSON can be way more compact than XML, and also we don't need URIs for our property types and links rels anymore, since we'd be defining our own special JSON format (application/uma-config+json) and within this namespace, our property names are unique and controlled by us.

Thoughts? Also, does anyone know if this would be strictly compatible with hostmeta or whether we'd be extending it somehow?

Eve

Eve Maler http://www.xmlgrrl.com/blog
+1 425 345 6756 http://www.twitter.com/xmlgrrl

_______________________________________________
WG-UMA mailing list
WG-...@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-uma

Reply all
Reply to author
Forward
0 new messages