Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

FSP_AFTER_LOGIN_URL not working for deep linking and redirect after APEX 5 upgrade

tfaJan 25 2016 — edited Jan 27 2016

Since upgrading to APEX 5 the use of FSP_AFTER_LOGIN_URL is not working to redirect/deep link.

We've setup a suite of applications to use a share login page for all applications.  When a user navigates to one of the applications in the suite if they do not have a current valid session then the common/shared login page is shown so the user can authenticate.  Then once authenticated the FSP_AFTER_LOGIN_URL logic has been used to redirect the user to their intended application.

For example application 350 is the common application where the shared login page lives.  And application 700 is the application the user wants to access.

Typically we've had URLs like the following with FSP_AFTER_LOGIN enabling the navigation to application 700 once authenticated through application 350 login page.

f?p=350:101:::::FSP_AFTER_LOGIN_URL:\f?p=700|1\

What is now happening is the URL f?p=350:101::::::   is being used but no FSP_AFTER_LOGIN is be shown.

For tests I've tried to past the URL with the FSP_AFTER_LOGIN_URL included with values into the browser and cannot get it to function for redirect.  Thoughts?  Does APEX 5 still use FSP_AFTER_LOGIN_URL?  What are options here?

This is a big issue for me as it affects login navigation and linking to applications from email notifications.

Thanks,

Todd

This post has been answered by tfa on Jan 27 2016
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 24 2016
Added on Jan 25 2016
3 comments
1,486 views