Re: [dotnetopenauth] Starting with DotnetOpenAuth ...

[Andrew Arnott]

I suggest you start by skimming the oauth 2 spec itself.  It sounds like you'll be building enough apps and clients to make it well worth it to know exactly what you're doing.  Then the terms and samples used in DNOA should fit the mental model you'll be building up and it should fit nicely.

--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre

On Thu, Aug 2, 2012 at 10:05 AM, Tabish <mtsa...@gmail.com> wrote:

Hi ,

 

We are developing Set of service using Asp.net WebApi and we are planning to integerate DotNetOpenAuth in our applications.

The consumer of our services will be accessing those services from different clients and may use our services to integerate into their applications. They all will be authenticated and authorized using DotNetOpenAuth mechanism

 

How should i proceed. I was looking at the sample code but was not able to understand the flow.

 

I really appreciate some pointer here and i also want to bring into discussion best practices or design pattern to integerate things.

 

Thanks in advance.

 

--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/0NnqxOCNgoAJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotnetopenid?hl=en.

[Tabish]

Thanks Andrew for your response.

I was looking at the specs and the example provided for OAuth 2.0 .I wasn't able to run that example however.

Here are a few things i want to clear here.

1) It seem that we may not have a CallbackURL in our case . Here is the flow . We provider our service to an organization and not any particular individual. Any individual will never have a direct access ti our Apis (like facebook , twitter where you are redirected to authenticate). So those organizations are our customers.

I want to know how this fits in. I may be starting from a wrong point here and that's why things are not fitting naturally.

Please suggest . I am initial phase of my design here and I am doing Proof Of Concepts here .I am sure i will be able to do appropriate changes to make things proper.

2) How do i intergate taht in my WebApi.

Thanks in advance.

Tabish

On Thursday, August 2, 2012 8:21:14 PM UTC-4, Andrew Arnott wrote:

I suggest you start by skimming the oauth 2 spec itself.  It sounds like you'll be building enough apps and clients to make it well worth it to know exactly what you're doing.  Then the terms and samples used in DNOA should fit the mental model you'll be building up and it should fit nicely.

--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre

On Thu, Aug 2, 2012 at 10:05 AM, Tabish  wrote:

Hi ,

 

We are developing Set of service using Asp.net WebApi and we are planning to integerate DotNetOpenAuth in our applications.

The consumer of our services will be accessing those services from different clients and may use our services to integerate into their applications. They all will be authenticated and authorized using DotNetOpenAuth mechanism

 

How should i proceed. I was looking at the sample code but was not able to understand the flow.

 

I really appreciate some pointer here and i also want to bring into discussion best practices or design pattern to integerate things.

 

Thanks in advance.

 

--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/0NnqxOCNgoAJ.
To post to this group, send email to dotnet...@googlegroups.com.

To unsubscribe from this group, send email to dotnetopenid+unsubscribe@googlegroups.com.