OAuth Client Id/secret corrupted for 'Error handling'. Still flows are working

R Charan C
Tera Expert

OAuth Client Id/secret corrupted for 'Error handling'. Still flows are working, which are not supposed to work.
FYI, Making Oauth credentials or Outh Entity 'Inactive' is throwing the Errors and Flow is not working.

What is the reason for flows working with 'OAuth Client Id/secret' ?

1 ACCEPTED SOLUTION

Ramesh Lohar
Kilo Guru

The reason why the flows are still working even with corrupted OAuth Client Id/secret could be due to the following reasons:

- Caching: ServiceNow might have cached the OAuth tokens and is still using the cached tokens for authentication. This is why the flows are still working even though the OAuth Client Id/secret is corrupted.

- Token Expiry: The OAuth tokens might not have expired yet. OAuth tokens have a certain lifespan after which they expire. If the tokens have not expired yet, they can still be used for authentication.

- Token Refresh: If the OAuth Client has a refresh token, it can use the refresh token to get a new access token even if the original access token is corrupted.

- Inactive OAuth Entity: If the OAuth entity is made inactive, it will throw errors because the OAuth entity is no longer valid for authentication. This is why the flows are not working when the OAuth entity is made inactive.

- Error Handling: If the flows have error handling mechanisms in place, they might be able to handle the errors caused by the corrupted OAuth Client Id/secret and continue to work.

- Fallback Authentication: If the flows have a fallback authentication mechanism in place, they might be using the fallback authentication when the OAuth authentication fails.

To resolve the issue, you might need to clear the cache, ensure that the OAuth tokens are expired, check the refresh token, make sure the OAuth entity is active, check the error handling mechanisms, and check the fallback authentication mechanisms.

For ServiceNow Live Classes, Books, Sample Resumes, Interview Questions, CSA Quizzes.
And getting better services's on ServiceNow you can visits our website.
Please visit : https://nowkb.com/home
Our Website :https://nowkb.com/home
nowKB.com

View solution in original post

1 REPLY 1

Ramesh Lohar
Kilo Guru

The reason why the flows are still working even with corrupted OAuth Client Id/secret could be due to the following reasons:

- Caching: ServiceNow might have cached the OAuth tokens and is still using the cached tokens for authentication. This is why the flows are still working even though the OAuth Client Id/secret is corrupted.

- Token Expiry: The OAuth tokens might not have expired yet. OAuth tokens have a certain lifespan after which they expire. If the tokens have not expired yet, they can still be used for authentication.

- Token Refresh: If the OAuth Client has a refresh token, it can use the refresh token to get a new access token even if the original access token is corrupted.

- Inactive OAuth Entity: If the OAuth entity is made inactive, it will throw errors because the OAuth entity is no longer valid for authentication. This is why the flows are not working when the OAuth entity is made inactive.

- Error Handling: If the flows have error handling mechanisms in place, they might be able to handle the errors caused by the corrupted OAuth Client Id/secret and continue to work.

- Fallback Authentication: If the flows have a fallback authentication mechanism in place, they might be using the fallback authentication when the OAuth authentication fails.

To resolve the issue, you might need to clear the cache, ensure that the OAuth tokens are expired, check the refresh token, make sure the OAuth entity is active, check the error handling mechanisms, and check the fallback authentication mechanisms.

For ServiceNow Live Classes, Books, Sample Resumes, Interview Questions, CSA Quizzes.
And getting better services's on ServiceNow you can visits our website.
Please visit : https://nowkb.com/home
Our Website :https://nowkb.com/home
nowKB.com