If I recall, IdSvr can pass the user directly through to an external Identity Provider if you pass idp: in the &acr_values on the token request.
For this to work nicely I figure the acr_values need to be set depending on the button clicked on the client.
Unless I'm mistaken I can't see a way to do this nicely in the current sample without a pretty big re-factor because the settings are not an exposed public property and are set on page load. The settings.acr_values would be required to be set based on the button clicked.
One option is to modify the redirectForToken function
But I'm sure there is a cleaner, nicer way to do this that is perhaps already supported by the library...and was wondering if you guys can direct me to it.
If I recall, IdSvr can pass the user directly through to an external Identity Provider if you pass idp: in the &acr_values on the token request.
For this to work nicely I figure the acr_values need to be set depending on the button clicked on the client.
Unless I'm mistaken I can't see a way to do this nicely in the current sample without a pretty big re-factor because the settings are not an exposed public property and are set on page load. The settings.acr_values would be required to be set based on the button clicked.
One option is to modify the redirectForToken function
But I'm sure there is a cleaner, nicer way to do this that is perhaps already supported by the library...and was wondering if you guys can direct me to it.
Thanks