Sorry my late night ramping don’t help…
I’m developing a custom web application, it uses the Okta SIW to authenticate users and then launch them into my custom web application. In this we application, I make an Okta API call to pull back the assigned applications and display them to the user. This API call pulls back the the Okta hard coded links e.g. https://dev-<number_here>.oktapreview.com/home/office365/0oab6f5sod7FfkCEH0h7/aln8l90mj9E52ZAZQ0g7.
Now if this application is SAML all works wonderfully. If this application is integrated via SWA and the user has the okta plugin installed, they go to this hard link which then redirects them to the real application URL and the plugin does its magic.
If the user doesn’t have the okta plugin installed, it stops at the Okta dashboard rather than redirect them to the destination. We want to keep users flowing through our custom web app, rather than ever be redirected to the Okta portal (except for a temporary redirection). It would cause a poor potential experience if the web app went live as users will be taken to the okta portal which they might not be familiar with.