[Openid-specs-ab] [Bitbucket] Issue #835: Clarify the expected JSON type(s) of "value" and "values" in the claims request JSON object (openid/connect)

[Nat Sakimura]

A naive question.

What is the guidance between the requesting claims in 'claims' request
parameter and the request object?

>From what I see, 'claims' request parameter features are completely covered
by request object. Main differences are that request object can specify
other parameter such as response_types as well as other security parameters
and can be signed (it is a compact serialized JWS), while 'claims'
parameter is form encoded.


2013/5/30 Michael Jones <issues-reply at bitbucket.org>

> **
>      [image: mbj]  *Michael Jones* commented on issue #835:  Clarify the
> expected JSON type(s) of "value" and "values" in the claims request JSON
> object<https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value>
>
> Fixed #835<https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value>- Clarified requirements on using "value" and "values" qualifiers when
> requesting specific values for individual claims.
>
> → <<cset 6af1216a68a0<https://bitbucket.org/openid/connect/commits/6af1216a68a0>
> >>
>  Status: new resolved   View this issue<https://bitbucket.org/openid/connect/issue/835/clarify-the-expected-json-type-s-of-value>or add a comment by replying to this email.
>     Unsubscribe from issue emails<https://bitbucket.org/openid/connect/issue/835/unsubscribe/Nat/6c4f45461cac10ce372f1f81a7903130e0898f5c/>for this repository.   [image:
> Bitbucket] <https://bitbucket.org>
>



-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130603/677b23ef/attachment.html>