Hello All,

The purpose of this post is to get some opinions of an idea I had for a Pseudo single sign on solution for my company's portals. I am wondering if the idea is worth pursuing or if there is a better way to do it. If it is a sound idea, is there anyone out there that has implemented something similar or documentation on how to develop an equivalent solution.

So here is the situation:

We currently have an Intranet site that is currently becoming the main online resource for our employees. We also are planning on implementing a public portal to display information about projects that employees are currently working on. The intranet site uses windows authentication, while the public portal will not be tied to the domain for obvious security reasons, which brings me to the problem:

We would like the employees to be able to edit the public portal from a link on their intranet homepage, without being required to login with a different username and password via forms authentication. 

Proposed solution:

Create an ASPX page that uses the current windows identity to get the portal address, username and password from a lookup table and post it (via sol) to the login form of the corresponding dotNetNuke portal. The username will not be tied to or match the windows username and the password will be a randomly generated string.

Has something like this be done before or is this a horrible solution?

If this all seems reasonable, the I have one more problem to contend with... All edits on the portals must be approved before being publicly visible. I know that some modules already support moderation, is there a way to enable moderation on all edits to a portal?

Sorry for the lengthy post, I hope it all makes sense. Please post any opinions, information, insults, you may...

Thanks

ITLackey

---

I like they way you are going with that. My only hesitation is, I would like to have the table that contains the list of domain usernames behind the firewall. This will ensure that only intranet users can query the table for usernames. Just another layer of defense against information disclosure. With such a module I would need to query that table from the public portal, correct?  If not, I apologize for my confusion, and ask for a more detailed explaination. I would prefer to not have to write an ASPX app to for this solution, just seems like overkill. We are using Sharepoint internally (simply because of the office intergration features) and was considering creating a webpart to do the SSO stuff.

---

I appreicate the input from both of you! My question is, do I need a custom login module? Is there something stopping me from creating a POST request to the /Default.aspx?ctl=login URL?

I need to extract all of the login for returning the login data from DNN. Which obviously must then exist outside of a module. Ideally, I should be able to provide a link to an employee on any intranet page that when clicked will direct them to the public portal and create an authenticated session. The intranet pages are NOT DNN portals, but will all be developed in ASP.Net. The first suggestion from workcontrol is pretty much what I am looking for, and the only drawback mentioned was viewable URLs with credintals in them. Again, couldnt this be mitigated using SSL and POST instead of a typically querystring? Is receiving the post what will require a custom mod, shouldnt I be able to post to the default login URL?

---