Hi @markdaku, welcome to the Developers Community, actually based on my understanding and experience, most IIQ OOTB connectors that rely on HTTP clients (especially REST-based ones like Oracle ERP/Fusion, Workday, and SuccessFactors) support connector-specific proxy settings via the application XML “assuming they use SailPoint’s built-in HTTP transport layer”
In the case of the Oracle ERP connector (which typically uses the Fusion REST API), the following application-level attributes are usually honored:
These are interpreted by the connector’s HTTP client (commonly based on Apache HTTP client) and apply only to this connector “not to the rest of IdentityIQ or other connectors” and this will work only if the connector implementation respects these properties, which is true for most modern REST-based connectors, including Oracle ERP, unless there’s a custom override or a different HTTP handling approach behind the scenes.
Just to note: TBH I haven’t tested or tried this specifically with Oracle ERP, but from the architecture and connector behaviour across versions 8.1–8.4, it should theoretically and logically work…
Curious to know , what exactly have you tried so far? did you apply these attributes at the application level, another place, or did you try a different method/way?
Let me know, and happy to help review it/them with you.
Have a nice and great one!