[Openid-specs-ab] SCOPE not selectable

[Preibisch, Sascha H]

Yes, thanks.

Sascha

From: John Bradley <ve7jtb at ve7jtb.com<mailto:ve7jtb at ve7jtb.com>>
Date: Monday, August 17, 2015 at 3:05 PM
To: Sascha Preibisch <sascha.preibisch at ca.com<mailto:sascha.preibisch at ca.com>>
Cc: "openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>" <openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>>
Subject: Re: [Openid-specs-ab] SCOPE not selectable

All scopes and claims are considered voluntary/optional by default.   If you use the claims request then you can mark a claim as essential.

When defining new scopes, you can define them as you like, but that is outside of Connect.

John B.
On Aug 17, 2015, at 6:51 PM, Preibisch, Sascha H <Sascha.Preibisch at ca.com<mailto:Sascha.Preibisch at ca.com>> wrote:

Thanks John!

I think in the end it really comes down to the app developer and the IdP for somehow let the user grant or deny certain SCOPEs/ permissions.

And yes, finding a general UI accepted by many parties will most likely not happen.

Thanks for the responses and I will take the section referenced below to write up a spec for our environment. We have more and more customers asking for the possibility to support that feature.

Sascha

From: John Bradley <ve7jtb at ve7jtb.com<mailto:ve7jtb at ve7jtb.com>>
Date: Monday, August 17, 2015 at 12:07 PM
To: Sascha Preibisch <sascha.preibisch at ca.com<mailto:sascha.preibisch at ca.com>>
Cc: "openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>" <openid-specs-ab at lists.openid.net<mailto:openid-specs-ab at lists.openid.net>>
Subject: Re: [Openid-specs-ab] SCOPE not selectable

The permissions you are asking about in Android are not really Connect scopes or claims.   They are permissions for the Google play store or OS to release information to the app, or for the app to perform actions.

The good news is that in Android M it is no longer a all or nothing proposition, you can deselect permissions the app wants.   However deselecting things will restrict app functionality as one would expect.

In OAuth there is no way to mark a scope as optional or required.

In Connect Sec 5.5.1 you can mark claims as essential to indicate to the AS that not returning those claims will cause the app not to function properly.

"By requesting Claims as Essential Claims, the RP indicates to the End-User that releasing these Claims will ensure a smooth authorization for the specific task requested by the End-User. Note that even if the Claims are not available because the End-User did not authorize their release or they are not present, the Authorization Server MUST NOT generate an error when Claims are not returned, whether they are Essential or Voluntary, unless otherwise specified in the description of the specific claim."

Getting IdP to agree on UI is a hard thing.  The Specification allows any scope or claim to be declined by the user.  Making IdP put it in the UI is something much harder.

John B.

On Aug 17, 2015, at 1:34 PM, Preibisch, Sascha H <Sascha.Preibisch at ca.com<mailto:Sascha.Preibisch at ca.com>> wrote:

Hi!

It may be an old topic but on the weekend I got a new Android phone and I attempted to install the LinkedIn and Twitter apps. Both apps requested about 10 permissions. Which I denied and therefore not installed.

I may be the only one who is annoyed by that but what is the reason why there is no effort in creating "optional" permissions? In the earlier development phase of OpenID Connect I joined a working group call and showed an example of an authorization page that required SCOPE "openid" but others were de-selectable by the resource owner. The others on that call did not appreciate that idea.

At IIW in March/ April 2014 Justin also mentioned the problem (what to do if requested SCOPE=LIVE KILL) but I do not see anyone addressing that or trying to change it.

Thanks for any thoughts on that,
Sascha
_______________________________________________
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-ab


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20150817/2440a082/attachment.html>