How do we get a custom (alternate) login page to show when a user goes directly to a UX Framework app page (/contextroot/p/web/app)? Even though we have defined an ALTERNATE_INDEX_HTML in TRIRIGAWEB.properties, it seems that the TRIRIGA default login page is shown when going directly to /contextroot/p/web/app. Should one define the login page separately for the UX Framework? We are using TRIRIGA 3.5.0.
We do not have alternate login page incorporated for the UX framework yet; that entry point uses its own login page which will always appear like the default. We are tracking an item internally to incorporate this functionality, essentially allowing you to build your own login view and utilize a core platform login component which we provide. I do not have a date that I can provide for this yet.
With that said, you may be able to authenticate via other means (SSO or an integration endpoint like CBA) and pass the appropriate session token on the header to get to a UX Framework view.