<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009hcflGCAQOkta Identity EngineAccess GatewayAnswered2023-10-31T21:55:09.000Z2023-10-12T18:53:21.000Z2023-10-31T21:55:08.000Z

LoganB.77615 (Customer) asked a question.

Migratating on prem application from IBM Webseal to Okta Access Gateway

Does anyone of have best practices or experience with replacing IBM Webseal with Okta Access Gateway? We currently redirect traffic through the reverse proxy(webseal) with URI routing to the back end application. Example: website.domain.com/app1, website.domain.com/app2, website.domain.com/app3, etc. I believe there is going to be custom policies that will need to written in order to achieve that same behavior with OAG but I currently don't know where to begin to start the process. From what I understand about OAG is the applications are handled like so app1.domain.com, app2.domain.com, app3.domain.com, etc.


This question is closed.
Loading
Migratating on prem application from IBM Webseal to Okta Access Gateway