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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using DNN as entry point to ASP siteUsing DNN as entry point to ASP site
Previous
 
Next
New Post
6/15/2007 10:28 AM
 

Sully - its a great idea and one that I have done in the past - here the issue the membership to these sites/applications is restricted and I had no hand in building them so they have no real membership system in the asp all the access is controlled by a product called Authentix which is an isapi filter that intercepts the calls to the server and checks if the person has permissions based on its programming

I need to find a solution to kick someone who may try to navigate directly to a page in the applications to a login - I would like to use DNN because it already has a membership system but its the asp pages that are giving me the fit


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
6/15/2007 11:36 AM
 

I apologize if the following suggestion sounds basic (I'm sure youve probably thought of it already) but I'm new to DNN, and fairly new to programming in general. I'm also not at all familiar with isapi filters. With the disclaimer out of the way, here's my thoughts.

If you're planning on removing the dependency from the Authentix product, how did you plan on accomplishing that? Is it as simple as disabling the filter on the server? If so, wouldn't the DNN membership & page permissions do what you're looking for? Even if you're using legacy membership data, you could write a custom membership provider that would allow for authentication against your data store. Anyone trying to navigate to a page with any permissions set (i.e. All Users page permission unchecked for view and edit) would be redirected to a login page.

Like I said, this is probably something you've already considered, but I thought I should suggest it anyway.

 
New Post
6/15/2007 12:06 PM
 

Well basically yes we disable the filter on the server - heres the rub ASP pages are run by a different program than .NET pages so if i hit a classic asp page the .NET program is never started so its authentication is never triggered - but otherwise you got it exactly - at least what i am tring to get it to do - got the membership stuff - got the userbase - just need something to tell my classic asp app 'hey are you authenticated "'


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
New Post
6/15/2007 12:54 PM
 

Yeah, I thought it sounded to easy to be feasible. Sorry I couldn't be of more help. Good luck!

 
New Post
6/16/2007 9:08 PM
 

Sully wasnt shooting you down it would work but it doesnt achieve what i need at this point - I think I am relegated to hiring someone to add a login function thing to everypage

the good news is i can use DNN as the front end at least


Dylan Barber http://www.braindice.com - Dotnetnuke development classes - skins and modules
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using DNN as entry point to ASP siteUsing DNN as entry point to ASP site


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