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
rtamalin
changed the title
SDK: Add a telemetry library support for the /authenticate API request
SDK: Add telemetry library support for the /authenticate API request
Jun 3, 2024
This underlying work for this was completed as part of #38.
The authentication approach was simplified to just requesting an updated client credentials set that includes a freshly generated auth token. The authenticate request requires a payload containing the client's id, and hash digest of it's instance id. These will be used by the server to validate that the client is registered with the server, and that the provided hash digest matches that of the client instance it provided when the client registered.
The auth tokens supplied by the server are now JWT's and it should be possible to check locally to determine if they have expired or now.
The server will fail with a HTTP 401 Unauthorized if an auth token is no longer valid, either because it has expired, or because the server had invalidated it, and it will be up to the client to obtain a new auth token using the authenticate request.
Leverage the /authenticate API request (#3) to implement authentication support in the telemetry library.
A client will use the /authenticate API request for one of the following reasons:
The headers of the re-authentication request must include the following items:
The payload of the re-authentication request contains the following items:
The telemetry client will be responsible for storing the updated authentication token so that it can be used in future requests.
The text was updated successfully, but these errors were encountered: