I have done it. Since authorization and authentication is orthogonal, it's
actually as straightforward as the two pieces separately. Just build a
DNOA authorization server, which uses ADFS for user authentication.
> I was wondering if anyone had done work to use ADFS as the identity
> provider and use DotNetOpenAuth to manage the authorization.
> The documentation seems to be in flux, so if there are any samples or
> articles someone can point me to, that would be most helpful.
> Thanks,
> Sam
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com<javascript:;>
> .
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com <javascript:;>.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
-- --
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
> I have done it. Since authorization and authentication is orthogonal, it's
> actually as straightforward as the two pieces separately. Just build a
> DNOA authorization server, which uses ADFS for user authentication.
> On Friday, May 4, 2012, sferrise wrote:
> > Hello,
> > I was wondering if anyone had done work to use ADFS as the identity
> > provider and use DotNetOpenAuth to manage the authorization.
> > The documentation seems to be in flux, so if there are any samples or
> > articles someone can point me to, that would be most helpful.
> > Thanks,
> > Sam
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DotNetOpenAuth" group.
> > To post to this group, send email to dotnetopenid@googlegroups.com<javascript:;>
> > .
> > To unsubscribe from this group, send email to
> > dotnetopenid+unsubscribe@googlegroups.com <javascript:;>.
> > For more options, visit this group at
> >http://groups.google.com/group/dotnetopenid?hl=en.
> --
> --
> 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
Yes, that sounds about right.
--
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 Fri, May 4, 2012 at 12:59 PM, sferrise <s.ferr...@gmail.com> wrote:
> If I look at the OAuthAuthorizationServer sample, this follows that
> model, except instead of using an OpenId provider WIF is used?
> The key for me is to use active federation with ADFS due to some other
> constraints which I think is where I am getting tripped up.
> On May 4, 2:01 pm, Andrew Arnott <andrewarn...@gmail.com> wrote:
> > I have done it. Since authorization and authentication is orthogonal,
> it's
> > actually as straightforward as the two pieces separately. Just build a
> > DNOA authorization server, which uses ADFS for user authentication.
> > On Friday, May 4, 2012, sferrise wrote:
> > > Hello,
> > > I was wondering if anyone had done work to use ADFS as the identity
> > > provider and use DotNetOpenAuth to manage the authorization.
> > > The documentation seems to be in flux, so if there are any samples or
> > > articles someone can point me to, that would be most helpful.
> > > Thanks,
> > > Sam
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "DotNetOpenAuth" group.
> > > To post to this group, send email to dotnetopenid@googlegroups.com
> <javascript:;>
> > > .
> > > To unsubscribe from this group, send email to
> > > dotnetopenid+unsubscribe@googlegroups.com <javascript:;>.
> > > For more options, visit this group at
> > >http://groups.google.com/group/dotnetopenid?hl=en.
> > --
> > --
> > 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
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.
> Yes, that sounds about right.
> --
> 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 Fri, May 4, 2012 at 12:59 PM, sferrise <s.ferr...@gmail.com> wrote:
> > If I look at the OAuthAuthorizationServer sample, this follows that
> > model, except instead of using an OpenId provider WIF is used?
> > The key for me is to use active federation with ADFS due to some other
> > constraints which I think is where I am getting tripped up.
> > On May 4, 2:01 pm, Andrew Arnott <andrewarn...@gmail.com> wrote:
> > > I have done it. Since authorization and authentication is orthogonal,
> > it's
> > > actually as straightforward as the two pieces separately. Just build a
> > > DNOA authorization server, which uses ADFS for user authentication.
> > > On Friday, May 4, 2012, sferrise wrote:
> > > > Hello,
> > > > I was wondering if anyone had done work to use ADFS as the identity
> > > > provider and use DotNetOpenAuth to manage the authorization.
> > > > The documentation seems to be in flux, so if there are any samples or
> > > > articles someone can point me to, that would be most helpful.
> > > > Thanks,
> > > > Sam
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "DotNetOpenAuth" group.
> > > > To post to this group, send email to dotnetopenid@googlegroups.com
> > <javascript:;>
> > > > .
> > > > To unsubscribe from this group, send email to
> > > > dotnetopenid+unsubscribe@googlegroups.com <javascript:;>.
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/dotnetopenid?hl=en.
> > > --
> > > --
> > > 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
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DotNetOpenAuth" group.
> > To post to this group, send email to dotnetopenid@googlegroups.com.
> > To unsubscribe from this group, send email to
> > dotnetopenid+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/dotnetopenid?hl=en.
On Fri, May 4, 2012 at 9:05 PM, sferrise <s.ferr...@gmail.com> wrote:
> Thanks - I'll give that a shot; appreciate the response.
> Sam
> On May 4, 3:02 pm, Andrew Arnott <andrewarn...@gmail.com> wrote:
> > Yes, that sounds about right.
> > --
> > 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 Fri, May 4, 2012 at 12:59 PM, sferrise <s.ferr...@gmail.com> wrote:
> > > If I look at the OAuthAuthorizationServer sample, this follows that
> > > model, except instead of using an OpenId provider WIF is used?
> > > The key for me is to use active federation with ADFS due to some other
> > > constraints which I think is where I am getting tripped up.
> > > On May 4, 2:01 pm, Andrew Arnott <andrewarn...@gmail.com> wrote:
> > > > I have done it. Since authorization and authentication is
> orthogonal,
> > > it's
> > > > actually as straightforward as the two pieces separately. Just
> build a
> > > > DNOA authorization server, which uses ADFS for user authentication.
> > > > On Friday, May 4, 2012, sferrise wrote:
> > > > > Hello,
> > > > > I was wondering if anyone had done work to use ADFS as the identity
> > > > > provider and use DotNetOpenAuth to manage the authorization.
> > > > > The documentation seems to be in flux, so if there are any samples
> or
> > > > > articles someone can point me to, that would be most helpful.
> > > > > Thanks,
> > > > > Sam
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "DotNetOpenAuth" group.
> > > > > To post to this group, send email to dotnetopenid@googlegroups.com
> > > <javascript:;>
> > > > > .
> > > > > To unsubscribe from this group, send email to
> > > > > dotnetopenid+unsubscribe@googlegroups.com <javascript:;>.
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/dotnetopenid?hl=en.
> > > > --
> > > > --
> > > > 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
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "DotNetOpenAuth" group.
> > > To post to this group, send email to dotnetopenid@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > dotnetopenid+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/dotnetopenid?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "DotNetOpenAuth" group.
> To post to this group, send email to dotnetopenid@googlegroups.com.
> To unsubscribe from this group, send email to
> dotnetopenid+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/dotnetopenid?hl=en.