Skip to content
This repository has been archived by the owner on Nov 1, 2024. It is now read-only.

No error on application key denial #46

Open
alexjhawk opened this issue May 10, 2021 · 1 comment
Open

No error on application key denial #46

alexjhawk opened this issue May 10, 2021 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@alexjhawk
Copy link
Collaborator

When an application key has either been deleted or revoked, there is no indication from the connector. It continues as normal and displays the same 'null' result as it would on success.
@alexjhawk alexjhawk added the bug Something isn't working label May 10, 2021
@alexjhawk alexjhawk added the help wanted Extra attention is needed label May 21, 2021
@alexjhawk
Copy link
Collaborator Author

The current best option appears to be an initial query to Thingworx at connector startup using a different Accept header in the HTTP request. If we use the application/xml value, we may receive a more verbose response with an indication of app key failure which we can interpret on the Flexy side.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexjhawk