Hi Shane
On 25/03/13 00:54, Shane B Weeden wrote:
There are several options. I've developed a few based on azn code flow with
custom "delivery" of the code, and also resource owner password credentials
flow with a public client id (although I personally don't like the idea of
ever presenting my r
This little presentation from last year talks about OAuth & mobile. In a
nutshell, it discusses using the authorization code grant and a redirect
uri with a custom scheme.
http://www.slideshare.net/briandavidcampbell/is-that-a-token-in-your-phone-in-your-pocket-or-are-you-just-glad-to-see-me-oauth
What I did in my OAuth 2.0 server environment was allow a client to
self-register without a redirect URI. If they do that, then use the azncode
flow, the azncode is displayed on the screen and the resource owner figures
out for themselves how to get it to the client. Quite similar in principal
to o
"Internationalization is the process of designing a software application
so that it can be adapted to various languages and regions without
engineering changes." (From
http://en.wikipedia.org/wiki/Internationalization_and_localization)
What this means in our case is that you'd want a string th
This approach is what we've implemented in a few places, most notably on
the hReader iOS app (code is in some branch or fork of
https://github.com/projecthreader/hReader, I'm told it's going to be
pulled into that main branch soon though). Here we pre-register the
hReader app with a single redi
FYI, the following version of this wording was incorporated into the OpenID
Connect Registration spec. I also found the phrase “internationalized UTF-8
string” ambiguous and so revised it. Also, UTF-8 is just plain wrong, as once
you’re in JSON you’re just dealing with Unicode strings, whether
Hi Justin,
At 08:11 25-03-2013, Justin Richer wrote:
"Internationalization is the process of designing a software
application so that it can be adapted to various languages and
regions without engineering changes." (From
There is some discussion about internationalization in RFC 6365.
Regards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/25/13 12:08 PM, Mike Jones wrote:
> FYI, the following version of this wording was incorporated into
> the OpenID Connect Registration spec. I also found the phrase
> “internationalized UTF-8 string” ambiguous and so revised it.
> Also, UTF-8 is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/25/13 9:11 AM, Justin Richer wrote:
> "Internationalization is the process of designing a software
> application so that it can be adapted to various languages and
> regions without engineering changes." (From
> http://en.wikipedia.org/wiki/Inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/25/13 9:14 AM, Justin Richer wrote:
> No problem, it's important that we be very precise about this bit
> of text. There are many terms in this space with subtle differences
> between them, so I'm glad to have others with more experience
> reading
Hi Peter,
Fair enough. I'll take an action item to read RFC 6365 and review the related
text accordingly.
The main point of my commentary was that the processing of the parsed JSON
would be the same no matter what the original encoding used was.
For what it's worth, I think that the two parag
11 matches
Mail list logo
