Hi @dustinedgecob! It looks like Oracle Integration Cloud is using the Client Credentials grant, which doesn't involve a browser login at all. That's probably why the browser prompt feels wrong. The OAuth 2.0 web service type in FME is designed for the Authorization Code flow (user-interactive), so switching to a Token web service would be closer. However, Oracle's token endpoint has an additional requirement: the client ID and secret need to be sent as a Base64-encoded value in the Authorization header, rather than as plain form body parameters.
The approach I'd recommend is building the token fetch directly in your workspace using an HTTPCaller. The pattern is similar to our article on connecting to Precisely's API:
Authenticating and Extracting Information from API calls with the HTTPCaller
Essentially:
- Use a BinaryEncoder to Base64-encode your
clientId:clientSecret string - Pass that into an HTTPCaller as
Authorization: Basic <encoded value>, with grant_type=client_credentials&scope=<your scope> in the form body, posting to Oracle's token endpoint - Use a JSONFlattener to extract the
access_token - Pass that as a Bearer token into a second HTTPCaller to call your actual Oracle Integration endpoint
I'm also looking into whether there's a case for product enhancements for future releases. Perhaps in how we connect to Oracle or our Token Web Services.
Hope this helps get you unblocked! Let me know if you have any questions 🙂