Ethan,
Ethan Adams wrote:
I am using Jetspeed 2 with an external SSO solution and have a question
related to the profiler.
The typical user scenario is that a user would navigate the portal as a
guest, and at some point, click a login link which would send them to an
external login page. We send a return URL in the login link so the user
ends up on the page they were on before logging in.
The problem is that a user may be on a page as guest that only the guest has
access to, and after they login, an error is thrown because they don't have
access to that page anymore.
The profiler and portal site component tries hard to fallback to a
reasonable page in this situation. At a minimum, it is supposed to fall
back to the root folder. What error are you seeing? What version of J2
are you using?
Is there anyway to setup the profiler to fall back to the parent folder of
the requested page if the user doesn't have access to the requested page?
There are different forms of fallback, depending on the situation, and
many potential solutions depending on your page hierarchy and
role/group usage. For starters, one can define a fallback page in the
root folder and a special version of the page for guest: this uses the
Profiler instead of Security Constraints to select the page, thus
avoiding the access issues up front. There are other more complex
solutions that might be of some utility as well. Finally, one can change
the security fallback behavior by altering the behavior of the
ProfilerValve.
HTH, will need more information about the specifics of your case to
advise further,
Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
