Yes, you can have session state protection enabled and send deep links via email. Anton and Hayden demonstrate in this slightly extended episode.
And, as usual, if you have comments, questions, or suggestions about this episode? Why not post them directly to Oracle? Here is this episode’s link
View Past Episodes
Full episode list on YouTube here.
Past Episodes
APEX #159: Recipes from the IG Cookbook
Marwa and Anton show you amazing things you can do with an Interactive Grid through recipes...
Read moreAPEX Instant Tips #158: Opening multiple browser tabs
Are you concerned about users opening multiple browser tabs? You should be...Marwa and Anton explain.
Read moreAPEX #157: Refreshing Region Plugin Regions
Anton and Marwa discuss how to make region plugins regions refreshable. Anton provides a boilerplate plugin...
Read moreAPEX Instant Tips #156: Informing users about background processes
Anton and Marwa discuss Background processes: informing users of what is happening and what occurs upon...
Read moreAPEX Instant Tips #155: About icons and buttons builder
We have extended the Universal Theme application to allow more customization within the icon and button...
Read moreAPEX Instant Tips #154: How to Recenter a Map Region
What is this episode about? Hint: Initial position in zoom, isn’t enough…
Read moreAPEX Instant Tips #153: Everything you always wanted to know about combobox but never thought to ask
With Combo boxes, you must manage your business rules and watch for multi-user concurrency issues. Anton...
Read moreAPEX Instant Tips #152: APEX.debug
In this episode, Anton and Marwa compare Console.log, APEX_debug.log, APEX_debug.message, and APEX.debug.setlevel.
Read more
Nice informations .
May be you have a hint for me about “strange” behaviour whe I use deep linking in an socialSignIn driven APEX APP. If a spezific page is secured/authorized – deep link doesn’t work if not it work like a charm. The APEX Version is 24.1?
Hi Thorsten,
Deep linking can be very challenging. If a page requires authentication (authN) it will redirect to login. If you have enabled deep linking in your application it should work even with social sign-on. If the page has an authorization (authZ) scheme, you will only get access to the page if you pass the authZ requirements. The extra challenge is related to passing parameters to the page. If the page or any of the parameters require a checksum (session state protection is enabled), you must include the checksum in the original request (before you are redirected to social sign-on). This means that the SSP settings must allow the checksum to be at the application or user level (not the session level). If it is at the user level, then the user that logs in must be the same as the user that the checksum was generated for. This can all be very difficult to accomplish and can take a significant amount of trial and error the first few times you try to get it working.
I hope this helps. If you provide more detail I may be able to give more specific advice.
Best of luck,
Anton