Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...SAML .NET Toolkit SAML .NET Toolkit
Previous
 
Next
New Post
10/23/2013 11:46 AM
 

Hi Everyone

About to embark on a Single Sign On project on DotnetNuke using the Component Space SAML 2.0 .NET toolkit integrating with ADFS.  We have partnered with another company in our industry which will be the Identity provider (IP). We will be the service provider (SP).

The process will work as follows:

1. The user is logged into a web site at the IP and clicks on a link to our third party application.  This directs them to the landing page for the partner service they want to access.
2. The partner web service receives an http GET request and attempts to authenticate the user.  However, the initial request contains no authentication information so the service re-directs the browser to the Federation Server.
3. The federation server determines that the user is trying to login using Single Sign-on from the web site and re-directs the browser to that web site to provide credentials.
4. The web site validates that the user is logged in and builds a set of claims.  These are signed and sent back to the browser to post to the Federation Server.  Note: If the user is not logged into the web site they will be presented to login.  This may occur is a user has bookmarked a web page on the partner site.
5. The Federation Server validates the claims provided by the web site and generates the credentials necessary to access the third party web site.  These credentials are built into the set of claims agreed with the service partner.  The claims are signed using the agreed private key and are sent back to the browser.
6. The web browser posts the signed claims to the partner web site, which is now able to authenticate the user and display the web application.

Does anybody have any experience or recommendations on what the best approach with this is considering that we already use the DNN membership provider & database and we have registered users. All our modules rely heavily on DNN profile properties so not a straightforward call with claims to call on the correct data for that user.

Just starting to get my head around how this will work so any pointers or advice is appreciated.

Cheers

 
New Post
10/23/2013 2:16 PM
 
John,

I actually just got done with a DNN integration using the SAML .NET Toolkit. It is a very interesting process, and how you work with DNN will really vary. My details are way too long to list here, but feel free to e-mail me at msellers@iowacomputergurus.com if you want to have a quick discussion.

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...SAML .NET Toolkit SAML .NET Toolkit


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out