Idea Summary
Allow developers to instruct APEX to preserve/rejoin a session using the browser session cookie no matter what.
Use Case
For a public app with premium features accessible if someone is signed in, as for example this very “ideas” app, there are no reasonable settings for the Rejoin Sessions mode that will allow the following situation to work.
- App has a public detail page model
https://$adbdns/ords/r/$workspace/$app/details?param=$p
(for example, this idea https://apexapps.oracle.com/pls/apex/r/apex_pm/ideas/details?idea=FR-2924
)
- User signs in
- User visits a bookmarked link for any detail page as in point 1.
Under all scenarios, APEX refuses to preserve the session, which looks to the user as if she has been logged out.
Preferred Solution (Optional)
Add a new mode alongside "Rejoin Public Sessions" and the confusingly-named "Rejoin All Sessions" which eliminates all the weird conditions designed to prevent URL hacking. Sometimes the ability for a user to easily formulate a URL is actually a feature.
Current workarounds include: implementing rejoin sessions ourselves using ORDS or hacking it using anchors, which only currently works because the latest version of theme_42.js:scrollTo is more tolerant of non-existent anchors than earlier versions were.