Hi,

I have gotten MPUS-X running on my installation, with only a few tweaks and some external issues causing trouble. I'm posting to track down an issue and ask a question, which may be related.

Our installation contains 30 portals, with various numbers of users. Some portals contain multiple aliases, in some cases as many as seven (to accommodate various www.* and *.com|net|org combos). I've learned that MPUS-X's cross-domain mode basically runs through the aliases and "logs in" the user to all domains. Is there any issue with the login process needing to redirect through so many domains - I know some browsers will alert when attempting too many. On logout the process will stop and indicate an "unresolving redirection". Could this be resulting from the number of aliases?

The question I have relates to portals participating in two Shared Areas. I have two SA which represent organizationally-separated portals. I have one portal that appears in both SAs to allow some users to participate in both Areas:

(fakey Venn Diagram)
/---------\ /----------\
| SA1 - portal - SA2 |
\---------/ \-----------/

In setting this up, I found that role settings on the shared portal would be lost and needed to be reset. Is there a problem with having a portal sit in the middle of two SAs (and could it result in the "unresolving redirect" issue above)?

Thanks
Dave

The "unresolved" error is caused by one of the aliases not resolving correctly in DNS. The same error should actually occur during login.

I've opened every alias in my PortalAlias table and all are resolving.

The only item that is unusual is we have an alias that is redirecting to a different portal in the installation (with a different domain name). The domain was used in a campaign and is redirecting from the campaign portal to the main portal. The redirection is coming at the DNS level.

Could this be causing the redirection issue?

Yes, it's very likely that the redirect is causing the module to think that the alias doesn't resolve.

I'm beginning to suspect that it is the number of aliases. I've removed the redirecting aliases and am still getting the problem.

When the process stops, the url is like the following:

If I click Go in my address bar on this URL, the page does resolve to the starting alias' domain, logged out.

The process does not stop at the same alias, but at an alias about halfway through the table. Interestingly, I sometimes get aliases for domains I don't have in a Shared Area.

Any thoughts?

We'll add an option to define the aliases to use for the SSO process.

This option was added in version 3.1.x and if your experience an error during logout it means that one of the aliases doesn't resolve.

Simple workaround is to remove all unnecessary aliases - it's good for the portal, too.

I am also running into this redirect problem running 2.1.18. All of my aliases work, but when I try to log out as an admin, it attempts to run through so many aliases that I get the redirect error.

Has this option been added? If so, which version and how do we access this functionality?

Thanks!

I am also running into this redirect problem running 2.1.18. All of my aliases work, but when I try to log out as an admin, it attempts to run through so many aliases that I get the redirect error.

Has this option been added? If so, which version and how do we access this functionality?

Thanks!

Looks like you answered this while I was trying to post my question yesterday... So we will have to upgrade to 3.1.x to get this bug fix?

Dos 3.1.x still support DNN 5.6.3?

3.1 requires dnn 6.x

Regardless of this option you should clean up your aliases.