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 the DNN user info in another page.Using the DNN user info in another page.
Previous
 
Next
New Post
6/22/2006 8:25 PM
 

Hi,

Im developing a portal with DNN.  However DNN is only going to be used as a wrapper.

 

I have separate asp pages that are various order entry screens and the like.  That will be displayed in iframe on the dnn screen.  I do not want to make modules out of these screens.

What I need to happen is use the dnn login to validate users for my other asp pages.  So the roles and users will be set up in DNN but will also be used by my pages do determine functionality. 

Is there any way to access the user information dnn stores from my pages.  I need to get the user name and password of the person logged in.  Then allow them to see the appropriate information on my asp pages.

I hope that makes sense thanks in advance for any help.

 

Joe.

 
New Post
6/23/2006 5:36 AM
 

That sounds like a round about convoluted way of doing things, especially when DotNetNuke is a framework designed to do exactly what you are trying to do. Why would you revalidate a user and password information when you can use the built in security model including user authenticated users, edit modes and roles?

Before you seriously consider your approach, considering taking 15 minutes to view Creating Your First Module on www.traincert.net  It is slightly outdated material but the general concepts still apply. It will save you hours, if not days and weeks of frustration if you wrap your application with DotNetNuke, not the other way around.

I hope this is of some help to you.


Dwayne J. Baldwin
 
New Post
6/23/2006 7:48 AM
 

There is absolutly no secure way to do what you want to do

I recommend you upgrade tyour classic asp application to ASP.NET 2.0, then you could use ASP.NET membership to share the login info

Even better would be as djbaldwin said, convert your app to DNN modules. You do not need to implement DNN DAL, this is just good design practise, you can keep your current data access methods and only rewrite the GUI in DNN style ASCX user controls


Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
6/25/2006 6:43 PM
 

GuitarDude,

I am in the same situation. I am also going to load the old site into an ifram and use DNN as the frontend. I will on the other hand make the old site moduler over time.

That being said, it appears that they there will soon be a fix to the current IFrame module that will allow parameters to be passed through the query string. From the screen shots, it appears that one of the parameters that you can use is UserId.

As far as looking up the currently logged in user in your old app, you really only need the UserId. I would not pass the password in the query string. If the user has already logged in through DNN, then passing the UserId to look up specific information is all you need. If you currently have a user table for the old app where you will need to look up information specifi to the user, then i would just create a reference field in the Users Table of the old site that links the user to the DNN user Table. Then when you pass the UserId you can do a quick look up on the currently logged in user.

djbaldwin,

For you question about why would you want to do this? Consider that in my case i will be transiiting from the old site to the DNN framework over a period of time (I have multiple application based intranets that need to be combined). My current intranets are too big to just create a module over night and do as you say with using the DNN framework out of the box. So as i build my modules i will take advantage of DNN's security by making it the single sign in for the multiple intratnet sites. Then overtime i will slowly convert the IFrame to the actual module and kill off the old intranets. That being said i still need to know who is logged in when they are working on an application in the old site. Passing the UserId through the query string will allow you to look up your user in your old site while still using DNN's framework.

 
New Post
6/25/2006 6:43 PM
 

GuitarDude,

I am in the same situation. I am also going to load the old site into an ifram and use DNN as the frontend. I will on the other hand make the old site moduler over time.

That being said, it appears that they there will soon be a fix to the current IFrame module that will allow parameters to be passed through the query string. From the screen shots, it appears that one of the parameters that you can use is UserId.

As far as looking up the currently logged in user in your old app, you really only need the UserId. I would not pass the password in the query string. If the user has already logged in through DNN, then passing the UserId to look up specific information is all you need. If you currently have a user table for the old app where you will need to look up information specifi to the user, then i would just create a reference field in the Users Table of the old site that links the user to the DNN user Table. Then when you pass the UserId you can do a quick look up on the currently logged in user.

djbaldwin,

For you question about why would you want to do this? Consider that in my case i will be transiiting from the old site to the DNN framework over a period of time (I have multiple application based intranets that need to be combined). My current intranets are too big to just create a module over night and do as you say with using the DNN framework out of the box. So as i build my modules i will take advantage of DNN's security by making it the single sign in for the multiple intratnet sites. Then overtime i will slowly convert the IFrame to the actual module and kill off the old intranets. That being said i still need to know who is logged in when they are working on an application in the old site. Passing the UserId through the query string will allow you to look up your user in your old site while still using DNN's framework.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using the DNN user info in another page.Using the DNN user info in another page.


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