We needed a bit of time to get OAuth running as well. For us it was the ClientID that didn’t match.

I would analyse the token with a tool like jwt.ms: Welcome! and then compare the ClientID with what you defined in IFS.

@Remo Thanks, just looking at that guide again and in the middleware server area under identify provider - IFS Database,  shows all the details but mine is blank. My details are  showing under the identity provider of Azure Active Directory…..?

I think you have to set up AD authentication instead of database. It would cause quite a few changes though.

However, in IFS10 you can use basic authentication, why do you want to use OAuth?

@rosscortb  Because I can’t get basic authentication to work. It used to work but stopped. 

API url is active, the username and password are correct but I get a 401 error.  When I paste the url in a browser it works fine. 

In my experience it’s easier to get Basic Auth running, I would recommend to look into that instead of OAuth.

@Remo will do, I think since the security team turned on accessing IFS Enterprise Explorer via SSO its stopped working. 

Then maybe check the FND_USER_TAB for the user you’re using. In the column WEB_USER there might be an email address indicating it’s using AD SSO. If you can, replace it with the value of IDENTITY and see if Basic Auth is working again.

@Remo