Additionally: This begs the question, why not just do SCIM here? CloudFoundry's UAA has a SCIM class for OAuth clients that they use for dynamic registration today.
-- Justin On Feb 4, 2013, at 4:25 PM, Mike Jones <[email protected]<mailto:[email protected]>> wrote: Now that we're returning the registration state as JSON, it's pretty inconsistent for the registration request to instead be form-url-encoded. The case can be made for switching to JSON now - especially in light of possibly wanting to convey some structured information at registration time. I realize that this is a big change, but if we're going to do it, we should do it now. As a precedent, apparently SCIM requests are JSON, rather than form-url-encoded. -- Mike _______________________________________________ OAuth mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
