Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Connecting to API using by Client ID and Client Secret via HTTP Basic Authentication

Highlighted

Re: Connecting to API using by Client ID and Client Secret via HTTP Basic Authentication

New Contributor

@ pierre Villard - Hi- I went thru your article posted in below link -

https://pierrevillard.com/2016/04/12/oauth-1-0a-with-apache-nifi-twitter-api-example/

In our API guide , I found that API uses use the OAuth 2.0 standard to authenticate all requests

The APIs are all accessed via REST invocations and return results in JSON format. The API use the OAuth 2.0 standard to authenticate all requests To authenticate to the API endpoint, we will need a token we send with every API call. To retrieve a token please follow the steps below- Request an access token by sending your Client ID and Client Secret via HTTP Basic Authentication, using an HTTP POST request. The Client ID and Client Secret need to be encoded to Base64, using the UTF-8 character set, in the form of client_id:client_secret. A resource you can use for this purpose is https://www.base64encode.org/.

This string is then passed as the Authorization header. The API will respond with an access token Note: Tokens are only valid for one hour. After one hour a new token is required. Pass the token as the Authorization header to access the API resources: API resource data is returned:

I assume there were some more steps needed in between which is missing to make the correct flow.

Can you please guide

Don't have an account?
Coming from Hortonworks? Activate your account here