Quite a few times I see a questions regarding how to share authentication between Oracle APEX applications so the user does not need to log in a second time.
As long as your link between the applications share the session ID, the solution is simple - set the cookie name the same across your applications.
Shared components -> Authentication Schemes -> Edit current scheme -> Session cookie attributes -> Cookie Name
This can help release management as you can modularise your applications. You could have a simple login/menu application that links to all your other applications.
If you wanted you could provide access to your application suite using different authenication mechanisms.
ie - if you log into application B using DB accounts, you can still hop across to application A.
The drawback I've found is that post-authentication will only fire during your initial login (in the relevant application). This means you need to be aware how to handle and share your authorisation mechanisms.
Divide and conquer!
As long as your link between the applications share the session ID, the solution is simple - set the cookie name the same across your applications.
Shared components -> Authentication Schemes -> Edit current scheme -> Session cookie attributes -> Cookie Name
 |
| Set same cookie name across applications |
 |
| Possible application map |
ie - if you log into application B using DB accounts, you can still hop across to application A.
The drawback I've found is that post-authentication will only fire during your initial login (in the relevant application). This means you need to be aware how to handle and share your authorisation mechanisms.
Divide and conquer!