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...AuthNetNuke - The Easy Way To Integrate DNN and ASP.NET ApplicationsAuthNetNuke - The Easy Way To Integrate DNN and ASP.NET Applications
Previous
 
Next
New Post
1/18/2007 11:11 PM
 
Mahesh - I have it currently working as a DNN module you place on a page.  The page itself you will configure via normal page security to only be visible to the roles that you wish to access your 2.0 application.  When these users hit the page, my module does some stuff, then they are redirected to your application and granted seamless access to whatever page you linked them to (providing the 2.0 is properly configured).  No code changes are required to the other application either.

The big advantages of my method over a custom role provider are:
  1. no code changes needed anywhere. 
  2. simple to configure.  Upload the module, put it on a page, configure the page security, and make a few web.config changes in the target app.  Simple.
  3. fast to implement.  10 mins or less.
  4. way cheaper than hiring someone to write you custom code
  5. SECURE - a custom role provider leaves your application open for access to any user of any portal in the DNN install providing they have a role of the same name and know the link to your application.  This is of primary concern in shared hosting scenarios.  My method is locked down so only those users you truly want get into your app.
host and admin users will not be redirected.  They will be given a screen to enter the target app url and some other parameters.  I am still coding this part, then need to work on the packaging and documentation.
 
New Post
1/24/2007 5:08 PM
 

Shawn -

How are you getting on with this? Is it near release?

thanks,

Steve


Steve White
 
New Post
1/24/2007 11:31 PM
 
Hi Steve,

Yes its quite close.  I have it working as a module now, so no core change are needed.  No code changes are needed in the external applications either.  There are some web.config things to set up though.  I have to finish writing the documentation and do some regression testing...I have developed it with DNN 4.4.0, and while it should work with any version of .NET 2.0 DNN, I can't say for sure until I test them.

I will package it for release as soon as I finish my documentation which should be this weekend.  By the end of next week you will be able to purchase it from my site via PayPal (SnowCovered later, but cheaper from my site).  It is called the AuthIntegrator.  

The module itself isn't pretty, but it does not need to be.  It works quite nicely and is secure, even in shared hosting scenarios.   Of course it is bound by the usual caveats of Forms Autrhentication and cookies...it will not work cross domain, but it will work as long as both the external .NET app and DNN belong to the same domain, regardless of whether DNN is the root of the domain, or both DNN and the app are virtual directories off the root.  The configuration required is slightly different in each case.

I also have planned for next release a version that will work cross domain.....but that is on the roadmap.
 
New Post
1/25/2007 6:32 AM
 

That's great Shawn, really looking forward to this.

To confirm will your module allow this:

- User logs into DNN and creates cookie with roles

- I include a link on DNN to another application on the same domain (or embed in an IFrame)

- The other application will recognise who the user is and will not require another login

- The roles that the user has in DNN will also be available in the other application

The last one will mean I can add some logic to the external app to check for a role string and allow/disallow functionality based on the role string from the DNN cookie. i.e it inherits DNN authentication and security role management. I can then almost use DNN as the master to control both users and security roles across multiple applications.

 thanks,

Steve


Steve White
 
New Post
1/25/2007 9:22 AM
 
The way it works is that you place my module on a page and configure the application URL and a Shared Secret (used like a password, I recommend a strong password such grc.com/passwords.htm provides).  You then set the page security to be visible only to the roles that have permissions in your external application.  When a user visits this page (from link or navigation) they are redirected to the URL you set.  In your external application you will include a HttpModule I have written (place in bin folder, add line to web.config) and add an App Setting (add line to web.config) which contains the same Shared Secret value configured in the module which will handle the authentication from there.

The other application will recognize who the user is and will not require another login

That is right. 

The roles that the user has in DNN will also be available in the other application


Yes.

The last one will mean I can add some logic to the external app to check for a role string and allow/disallow functionality based on the role string from the DNN cookie. i.e it inherits DNN authentication and security role management. I can then almost use DNN as the master to control both users and security roles across multiple applications.

Exactly.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...AuthNetNuke - The Easy Way To Integrate DNN and ASP.NET ApplicationsAuthNetNuke - The Easy Way To Integrate DNN and ASP.NET Applications


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