ResolverError returned in service node

XO Platform Builder Bugs
,
1

Hi,

We have instances where the service node throws ResolverError. This happens for a service node that is using password grant type Oauth2.

MicrosoftTeams-image (4)
MicrosoftTeams-image (4)350×194 3.14 KB

Screen Shot 2021-06-01 at 11.00.24 AM
Screen Shot 2021-06-01 at 11.00.24 AM783×253 22 KB

The weird thing here is, if we create a separate service node to get a token, then pass it to the other service node, it is working fine. Another thing, is that if the API returns 200 or 201, it succesfully processes the service node as shown below.

MicrosoftTeams-image (5)
MicrosoftTeams-image (5)556×381 8.39 KB

We can share a sample bot if it can help in the investigation.

Thank you.

2

Hello. Can we follow up on this

Thank you.

3

Can we follow up on this?
Just to add, it seems that the service node returns “Resolver Error” when the response does not have status code of 200 or 201.

4

Hello @pastapareo,

Please review the following post that should help with this issue:

https://test-discourse.kore.ai/t/failed-to-obtain-access-token-callback-message-when-testing-the-oauth-v2-authorization-mechanism/1061/6