You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have quickly added the integration tests for both public and private resource API (api/Resource/public and api/Resource/private) to validate the case when the API and the Server are not in the same app.
I always get the success status code from the public API, which is good, but the private API returns the internal server error due to the token validation failed, "No connection could be made because the target machine actively refused it". I ensure the token is valid and the Server is running properly since it returns the correct user info.
The interesting is, if I run the Server manually, all tests are passed. This means the token validation is success.
Is there something that I missed to get it run correctly?
The text was updated successfully, but these errors were encountered:
Hello @thomasduft
I have quickly added the integration tests for both public and private resource API (api/Resource/public and api/Resource/private) to validate the case when the API and the Server are not in the same app.
I always get the success status code from the public API, which is good, but the private API returns the internal server error due to the token validation failed, "No connection could be made because the target machine actively refused it". I ensure the token is valid and the Server is running properly since it returns the correct user info.
The interesting is, if I run the Server manually, all tests are passed. This means the token validation is success.
Is there something that I missed to get it run correctly?
The text was updated successfully, but these errors were encountered: