Re: Using multiple protocols and identifiers for authentication and resource access

On 12/27/12 12:23 AM, Peter Williams wrote:
> http://yorkporc.wordpress.com/2012/12/26/asp-net-visual-studio-2012-to-openlink-oauth/ documents 
> as far as I could get, using a Microsoft “production” library (a 
> wrapper around the dotnetopenauth library - used in conformance 
> testing). The lib allows one to fiddle with only certain aspects of 
> the protocol (the endpoint behaviours, mostly), demanding conformance 
> in other ways - from the way its objects and their interfaces are 
> constructed.
> The provider seems not to provide a oauth_token parameter by return, 
> upon completing authorization. I suspect it should reflect what its 
> given. Attempts to add it to the callback URI don't work, since its 
> removed by the authorization handler.

Here is a revised edition of the ODS OAuth provider documentation: 
http://web.ods.openlinksw.com/odsdox/ods_oauth_server.html

I'll make time to digest your post too.

Happy Holidays!

Kingsley
> Sent from Windows Mail
> *From:* Kingsley Idehen
> *Sent:* ‎December‎ ‎17‎, ‎2012 ‎6‎:‎47‎ ‎AM
> *To:* public-rww@w3.org, Peter Williams
> *Subject:* Re: Using multiple protocols and identifiers for 
> authentication and resource access
> On 12/14/12 5:35 PM, peter williams wrote:
>
>     Can you update your openid or oAuth provider proxies, and publish
>     the endpoints etc.
>
>     I've also built a multi protocol name linking site, multitenant,
>     arouNd hosted in the azure cloud, and talks upstream to most oauth
>     and openid ( and more enterprise ) protocols. By this means it
>     indirectly supports browserid and I'm hoping webid, if we can get
>     your gateway working again.
>
>     I also added an oauth guarded Api that might even cooperate with
>     your connection point manager.
>
>     Anyways Lots to play with as several layers of nameid linking occurs.
>
>     For legal/ patent reasons, I'm limited to the semantics and
>     methods of saml sp affiliations ( though we are relaxed about what
>     blog formats are used, sAml blobs or otherwise)
>
>
> Peter,
>
> For now, look at our current OAuth binding guide [1]. That said, we 
> are going to produce another that looks more like what you see 
> provided by other OAuth providers re. HTML flow etc..
>
> Links:
>
> 1. 
> http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtuosoOAuthServer 
> -- current docs (shows endpoint patterns etc..)
>
> Kingsley
>
>
>     Kingsley Idehen <kidehen@openlinksw.com>
>     <mailto:kidehen@openlinksw.com> wrote:
>
>     All,
>
>     Here is a simple (silent) screencast that demonstrates how a
>     system can
>     combine the features of OpenID, OAuth, Persona (but not covered in
>     this
>     demo), and WebID en rotue to providing read-write access to protected
>     resources published to an HTTP network such as the World Wide Web.
>
>     The screencast covers:
>
>     1. Associating 3rd party accounts with an ODS account -- note
>     accounts
>     can also be automatically created via WebID, OpenID, Persona,
>     OAuth etc..
>     2. Resource Access control scoped to specific identifiers for
>     Agents or
>     Accounts.
>
>     What happens:
>
>     1. I login to ODS using WebID -- since my ODS account is
>     associated with
>     one of my WebIDs
>     2. I connect my Twitter, LinkedIn, and Facebook accounts via the ODS
>     Profile UI for 3rd party account binding
>     3. I use the ODS-Briefcase UI to provide access to setup resource ACLs
>     4. Access the protected resource.
>
>     Screencast Link: http://bit.ly/XUkXx1 .
>
>     -- 
>
>     Regards,
>
>     Kingsley Idehen
>     Founder & CEO
>     OpenLink Software
>     Company Web: http://www.openlinksw.com
>     Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>     <http://www.openlinksw.com/blog/%7Ekidehen>
>     Twitter/Identi.ca handle: @kidehen
>     Google+ Profile: https://plus.google.com/112399767740508618350/about
>     LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>
>
> -- 
>
> Regards,
>
> Kingsley Idehen 
> Founder & CEO
> OpenLink Software
> Company Web:http://www.openlinksw.com
> Personal Weblog:http://www.openlinksw.com/blog/~kidehen  <http://www.openlinksw.com/blog/%7Ekidehen>
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile:https://plus.google.com/112399767740508618350/about
> LinkedIn Profile:http://www.linkedin.com/in/kidehen
>
>
>
>


-- 

Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Thursday, 27 December 2012 15:31:54 UTC