Hi,

I'm having some trouble figuring out if DNN has the capability to redirect a user that is being validated to a URL on a different portal within the same site.

For example, say I have PortalA and PortalB, and a User1 that has only access to PortalB. However, I do want to allow for the user to attempt to use the Login page for PortalA, and some logic to determine that the user needs to be directed to PortalB during or after the login process. So, if User1 visits the site PortalA.com and attempts to login, I want User1 to end up being validated and logged in to PortalB, and landing on the home page for PortalB.

Looking at the PortalSettings object, I can override the PortalId and the PortalName that goes into the UserController.ValidateUser and UserController.UserLogin methods, but that does not help with any redirection across two portals. I also took a look at the changing HomeTabId variable that is used for obtaining the RedirectURL and it seems that changing that to an Id that is for the Home Page does not work - because the HomeTabId is outside of the current portal, Globals.NavigateURL() does not give me the URL to the correct portal I want to be redirected to.

Additionally, there is a need to be able to determine on either PortalA or PortalB's login page, if the user logging in has access to both portals. If they do have access to both portals, then the user would be able to select (from a list, drop down, etc.) which Portal they are wanting to go to. From the selection, the user could then continue on to PortalA or PortalB FROM either PortalA or PortalB's login page as needed. I imagine that if the prior requirements can be solved, then this should be easily solved.

Just in case, there are business rules that dictate that we do need separate portals. Each portal has portal specific functionality, business logic engines, and navigation menus.

If anyone has any advice or foresight into this situation, it would be greatly appreciated!

Chris, thanks for the response.

I did eventually figure out a custom workaround.

I ended up writing an intermediary page with a module that handles the page redirection as needed. I'm setting up the information in the session on that page, after reading a login token stored in the database while sending over the token ID and username over query string. The user never sees that page, and the token is alive for a short duration that it shouldn't be something hijacked. The intermediate page also handles redirecting to the login page as needed if the user's token has expired or if they have reached the page by some means, since the URL is not openly visible.