I want to seamlessly link to, and transition to, a shared ADMIN application without having to do a second login dialog.
Assume that I have a “shared” ADMIN application (App ID = 1000) that manages common administrative data (e.g. settings, application internal security, etc.) that services multiple “client” applications CLIENT-A (App ID = 101), CLIENT_B (App ID = 102), etc. I want my users to be able to login to their specific client and then transition via button click to the ADMIN for that application without invoking the ADMIN login dialog, etc.
I envision the client “calling” the admin application and passing its APP_SESSION variable. Each client captures some meta data (e.g. App ID) and stores it in a shared table that the ADMIN application uses to distinguish which client it is servicing.
Is there a best practice that:
- Disables “login” validation in the ADMIN application or otherwise avoids requiring the login page?
- Pass and receive the CLIENT APP_SESSION so that the ADMIN application knows which data to present?
- Inherit a client session and adopt it as the admin session?