Hi Vikash,
Apologies, I should have updated the forum. I did manage to get it to work. Configuring the security log in the API GW gui, followed by an update in the integration server console to ensure Authentication and Authorization was selected worked.
I did find if I just updated it in the Integration server only, the configuration was lost when stopping and starting the integration server.
We can see success and failure of authentication when obtaining the token.
However, I do not obtain failed authorisation issues being logged. eg Asking for a scope you don’t have or not exists, as well as calling an API with a bearer token with the wrong scope.
I have set the server extended setting watt.server.oauth.log.authErrors to true and the error log is set for file.
According to the manual, I was expecting authorisation failure to be logged in the error log: Other errors, do appear in the error log, but not oauth authorisation ones.
Important Considerations for Using OAuth Features (softwareag.com)
This is what it says in the manual:
For OAuth authorization failures to appear in the error log, the watt.server.oauth.log.authErrors server configuration parameter must be set to true. By default, this parameter is set to false, meaning Integration Server does not write OAuth authorization errors to any log.
Is what I am trying to do considered to be an OAuth authorization failure?
#API-Gateway#API-Management#webMethods#Monday-challenge