Re: [dotnetopenauth] Is OpenID + self-provider recommended for our scenario?

[Andrew Arnott]

I can't comment on SAML vs. OpenID particularly, since I have no experience with SAML.  But lots of folks have used OpenID to achieve SSO within their organization of web sites (on both Internet and Intranet).
--
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, Jun 15, 2012 at 5:22 AM, Venkat <svs.v...@gmail.com> wrote:

Here's our situation:

• We own a main portal, developed in ASP.Net 4.0
  
• There are a few other web portals within our organization, which would like to use our portal for authentication & SSO. These portals could be in any platform: PHP, classic ASP, JSP, etc
  
• And there are a few more external portals for which also we would like SSO. These external portals are well-known in advance and they are in a closed environment: meaning they would not prefer login attempts using random public OpenID authentications.

I've been going through various articles on Internet, but I could not conclude which of the following is the best option for the above scenario:

• OpenID plus self-provider, using DotNetOpenAuth. Clients will trust only one OpenID provider: us.
  
• SAML, using a library like ComponentSpace (http://www.componentspace.com/saml)
  
• Any other better alternative?
  

All tips will be highly appreciated :)

--
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/-/ObasqP9rwQYJ.
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.