[Openid-specs-ab] AppAuth Fork
mike at gluu.org
Fri Jan 20 21:15:02 UTC 2017
Ok good points! Thanks for the feedback.
We did change the demo to align the names more clearly with generic
OpenID Connect jargon, but maybe it would be better to just include
On 2017-01-20 00:05, William Denniss wrote:
> Re: "Also, much of the stuff in OIDF AppAuth project is Google
> I really feel it's a disingenuous characterization to say AppAuth for
> Android has anything Google IdP specific. To the contrary we were very
> careful not to do this.
> The included *demo* uses Google as an example. But in a pure OIDC (w/
> OAuth for Native Apps & PKCE) standardized approach, so you can easily
> replace our issuer with your own. I've personally tried this with Ping
> and the Django OpenId Connect provider and both worked with only
> config changes.
> I'm definitely supportive of adding more demo providers to the
> included sample. The demo however isn't really a "normative" part of
> the SDK which is why I strongly dispute the above characterization.
> That aside: by all means fork and improve AppAuth (and the demo)! I'd
> love to see to see a pull request in the OpenID repo with your changes
> On Thu, Jan 19, 2017 at 9:11 PM Mike Schwartz via Openid-specs-ab
> <openid-specs-ab at lists.openid.net> wrote:
>>>> Google-specific URLs - not Google-specific APIs
>> It was the name of the variables that made the code a little
>> confusing... not the functionality or the URL's.
>>>> If Mike Schwartz made a pull request for the signature validation
>>>> across platforms, >> we would appreciate that
>> Ok, but it would be sometime in Feb. We're not done with the iOS
>> fork yet anyway.
>> - Mike
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
More information about the Openid-specs-ab