You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently planning to use YARP as a proxy to allow us to migrate existing WebAPIs from Siteminder to Ping Access. All individual apis will use OAuth2 going forward. But we will have a proxy that will support Siteminder authentication cookie and internally generate access token before forwarding the request to individual APIs. The individual APIs could be hosted on VMs or on Openshift container.
I was wondering, if we wanted to extend the YARP usage later on, when everything will be OAuth2 based, lets say to do pilot routing for new features only for specific users, is it possible to do it with current version of YARP?
So essentially incoming route will be same. But based on the user for which request is coming in, I want to reroute request to either destination 1 or destination 2. This destination 1 or 2 can be an entirely different route or reroute to a new version of existing API. So the cluster itself could also be entirely different. Please suggest how this can be achieved.
Thanks!
The text was updated successfully, but these errors were encountered:
hi,
We are currently planning to use YARP as a proxy to allow us to migrate existing WebAPIs from Siteminder to Ping Access. All individual apis will use OAuth2 going forward. But we will have a proxy that will support Siteminder authentication cookie and internally generate access token before forwarding the request to individual APIs. The individual APIs could be hosted on VMs or on Openshift container.
I was wondering, if we wanted to extend the YARP usage later on, when everything will be OAuth2 based, lets say to do pilot routing for new features only for specific users, is it possible to do it with current version of YARP?
So essentially incoming route will be same. But based on the user for which request is coming in, I want to reroute request to either destination 1 or destination 2. This destination 1 or 2 can be an entirely different route or reroute to a new version of existing API. So the cluster itself could also be entirely different. Please suggest how this can be achieved.
Thanks!
The text was updated successfully, but these errors were encountered: