validation and booleans

[aaronchi]

I'm trying to do an auth with omniauth-openid-connect and validation is failing because email_verified is coming back as "true" (String) in UserInfo and openid_connect validation is looking for a boolean value. It seems like the UserInfo initialization needs to handle converting strings to booleans if you are going to do this kind of validation.

[nov]

JSON String for the claim is invalid.
Which IdP is issuing the ID Token?

Sent from my iPhone

On 2014/03/22, at 4:45, aaronchi notifications@github.com wrote:

I'm trying to do an auth with omniauth-openid-connect and validation is failing because email_verified is coming back as "true" (string) and openid_connect is looking for a boolean value. I'm not sure where this is set but it seems like the library should be able to handle this.

�
Reply to this email directly or view it on GitHub.

[aaronchi]

Not for the claim, this is for the email_verified field. the response comes back with "email_verified" => "true" in the hash and then the validation fails. You need to convert strings to booleans when you initialize the UserInfo object.

[nov]

The raw JSON should include a boolean value, not a string.

Sent from my iPhone

On 2014/03/22, at 15:23, aaronchi notifications@github.com wrote:

Not for the claim, this is for the email_verified field. the response comes back with email_verified => "true" in the hash and then the validation fails. You need to convert strings to booleans when you initialize the UserInfo object.

�
Reply to this email directly or view it on GitHub.

[aaronchi]

Maybe it should, but it doesn't :) This is from google

[nov]

will report to them.

Sent from my iPhone

On 2014/03/22, at 15:31, aaronchi notifications@github.com wrote:

Maybe it should, but it doesn't :) This is from google

�
Reply to this email directly or view it on GitHub.

[nov]

Confirmed https://www.googleapis.com/plus/v1/people/me/openIdConnect returns invalid format of UserInfo response.
It's Google's bug.