Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The HTTP plugin provides different authentication methods for the defined Datapoints. Although, in some APIs the client request needs to provide authentication information, otherwise the server responds to a client with a 401(Unauthorized) response.

In the normal HTTP Basic Authentication. each Datapoint can provides a username and password to prove their authentication in (Authentication User, Authentication Password) fields. But some Servers provide tokens, the next 2 example will handle tokens in both (Basic Authentication, OAuth2 Authentication).


 Basic Authentication 

If Datapoint needs to provide a token in order to Get or Post request, the token should be added in the Additional HTTP Headers. Datapoint requests with the Authorization header that contains the word Basic word followed by a space and token.

Authorization: Basic YmRmODRjNzBhYzI0NDM5ZDgyOTE5M2FiMjI1NDBhMDE6OWI2MTYzMEQ3NmUxNEQ1Mzk0MjgwMTdkNzZBRjhmODY=



Basic authentication can also be combined with other authentication methods as explained in Using Multiple Authentication Types like Username and Password.

OAuth2 Authentication


If Datapoint needs to make calls from API that has OAuth 2.0 as authorization protocol you will need also an access token. When passing the access token in an Additional HTTP Headers with the Authorization header that contains the word Bearer word followed by a space and token.

Authorization: Bearer YmRmODRjNzBhYzI0NDM5ZDgyOTE5M2FiMjI1NDBhMDE6OWI2MTYzMEQ3NmUxNEQ1Mzk0MjgwMTdkNzZBRjhmODY=




  • No labels