We have configured Copilot to integrate with ServiceNow Knowledge to share KBA's articles in Teams.
We used OAuth2.0 and set up the configuration with a Client ID and Secret. However - to 'authorize' we are forced to enter a User ID/Password that authenticates via OKTA. This created an entry in the oauth_credentials table with both the Application Registry (client id/secret) and User (person who logged on to authenticate). Changing the entry to the Service Account for 'copilot' did not fix the problem. It is still connecting via the User that 'authorized' during the configuration.
This seems awkward because:
1) Using OAuth2.0 - should not require a User ID
2) The Application Registry record does have the OAuth Application User aligned to the record.
3) We should NEVER have a User responsible for an automated configuration.
Any ideas how to correct this misalignment?
Thanks!
