{"id":918,"date":"2012-12-28T16:50:36","date_gmt":"2012-12-29T00:50:36","guid":{"rendered":"https:\/\/self-issued.info\/?p=918"},"modified":"2012-12-28T17:01:20","modified_gmt":"2012-12-29T01:01:20","slug":"december-27-2012-openid-connect-release","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=918","title":{"rendered":"December 27, 2012 OpenID Connect Release"},"content":{"rendered":"

\"OpenID<\/span>New versions of the OpenID Connect specifications have been released resolving numerous open issues raised by the working group. The most significant change is changing the name of the “user_id<\/code>” claim to “sub<\/code>” (subject) so that ID Tokens conform to the OAuth JWT Bearer Profile specification<\/a>, and so they can be used as OAuth assertions. (Also, see the related coordinated change to the OAuth JWT specifications<\/a>.) A related enhancement was extending our use of the “aud<\/code>” (audience) claim to allow ID Tokens to have multiple audiences. Also, a related addition was defining the “azp<\/code>” (authorized party) claim to allow implementers to experiment with this proposed functionality. (This is a slightly more general form of the “cid<\/code>” claim that Google and Nat Sakimura had proposed.)<\/p>\n

Other updates were:<\/p>\n