A Power Apps custom connector configured with OAuth2 against an IFS Cloud core environment fails when tested, even though the exact same OAuth2 setup (both authorization code and client credentials flows) works fine when tested directly in Postman.

All FAQ questions / Integrations and APIs

Answer

In a confirmed case, this turned out to be simply incorrect authentication/token URLs configured in the Power Apps custom connector itself, not an actual incompatibility between Power Apps and IFS Cloud's OAuth2 implementation. If Postman works with the same credentials and flow type but the Power Apps custom connector doesn't, double-check every authorization/token endpoint URL entered in the connector's configuration first, since a working Postman test rules out the server-side OAuth2 setup and points toward a connector-configuration mistake instead.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions