Hi, Ved. It's impossible in 3.0.2 for SAML flows, as far as I know. For OIDC you have option to pass `acr_values` url query parameter which in case of Gluu should contain name of custom script implementing auth method you need. In case of SAML flows default oxAuth auth method will always be used, and no parameters are passed to it which would allow to select some particular script. In CE 3.1 there should be a new feature which allows you to pass `entityid` of SP requestor to that default auth method. We also have a basic script which can "route" authentication flow to other custom scripts, based on some condition, which you could customize. So combining those 2 features, you may be able to select a proper auth method based on `entityid` of SP. No ETA for this feature at the moment, though.

Thanks Aliaksandr. This was helpful.

Alex is right that OpenID Connect would give you more flexibility to specify a specific custom script during authentication (at which time you could us the getPageForStep method of the interception script to display a different page. However... if the user already has a session, when navigating to the 2nd page, no login page is display (i.e. there is SSO). This could be a use case for UMA. If you use an UMA RPT access token, as part of the "claims gathering" flow, it might give you even more flexibility to route to a different authentication workflow, depending on the context.