DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Accessing another site via a DNN site - how to validate a user?

 1 Replies
 1 Subscribed to this topic
 40 Subscribed to this forum
Sort:
Author
Messages
New Around Here
Posts: 5
New Around Here

Hi - I am re-posting this from another forum hoping someone might be able to help :-)

Hi

apologies in advance, i am not a developer! We have developers currently building some functionality for us and I am looking for some documentation/help..... our main site is a DNN one and users register accounts for secure access. The new functionality that we are adding will be accessed by a user clicking a button in our DNN site, which will take them to the new site. We need a way to authenticate those users on the new site, using their DNN credentials as we want this to be a seamless user experience.

I am hoping that when a user gets passed to the new site, that the request could include a token of some sort that we can validate and use to verify their identity.
(The token might be in a cookie or a url parameter or a header field for example.)

When they are finished their tasks on the new site. they will click a link/menu item to return to where they came from in the DNN site and once again, we will need to know who has arrived on that page so we know what information can be shared with them.

I hope that makes sense and if anyone can point me towards something that i can share with our developers I would be really grateful!

Thanks,

Lisa

Veteran Member
Posts: 360
Veteran Member
Helpful Replier
Helpful Replier
Thanks for being such a helpful replier!
MVP
MVP
You're an MVP!
Lisa, this is most likely possible, but it really depends on the capabilities of the other (non-DNN) site. Can you share a bit of insight on what that site is built on? Is it another CMS, an e-Commerce site, a custom site? What is the tech stack? Does it have a built-in authentication mechanism? Is that authentication mechanism extensible?

Do you really need to authenticate the user on the other (non-DNN) site or just keep track of who the DNN user is that was referred? These could be completely different propositions and one (just passing user info to the other site) is significantly simpler than the other (authenticating the user on the other site using DNN as the external auth system).

Given a bit more context, I'm sure we could help with more specific information. :)

David Poindexter


Creator:


These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

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

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. 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.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved