We have a situation wherein, once the user logs-in we check to see if
they have signed a privacy consent agreement. If the have, they proceed
to the normal site welcome page for their profile and if they have not
agreed, they are sent to a consent page where they have the option of
consenting or logging out.
Is this something that fits with what you are doing or could be adapted
to meet your needs?
Ron
On 20/12/2010 10:25 AM, Randy Watler wrote:
Amyz:
Normally, one uses the root level default-page.psml as landing pages
for default authenticated, guest, role, group, and user-specific cases:
default:
<psml root>/default-page.psml
guest:
<psml root>/_user/guest/default-page.psml
role:
<psml root>/_role/manager/default-page.psml
group:
<psml root>/_group/customer/default-page.psml
user:
<psml root>/_user/amyz/default-page.psml
As mentioned on your other threads, the effective profiling rules and
constraints select which page to display.
Regarding that property, it is used when you need a programmatic
redirect after a login has been invoked. It is a portal request
parameter that indicates where the user is to be redirected and is
normally needed when there is some complex landing page requirement
that cannot be satisfied using the profiler alone as above.
Randy
On 12/20/2010 5:58 AM, anyz wrote:
While using J2 login portlet i need to redirect user to custom page
after
successfull login. Where do i configure page to land after successfull
login. My understanding for both successfull and failed login the
LoginProxyServlet redirects to LoginRedirectorServlet that redirects
user to
path defined in session by attribute
"org.apache.jetspeed.login.destination".
Where can i configure this "org.apache.jetspeed.login.destination" in
configuration files?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
