Skip to content

Latest commit

 

History

History
81 lines (73 loc) · 3.73 KB

HowToFetchToken.md

File metadata and controls

81 lines (73 loc) · 3.73 KB

How to fetch tokens

Get your service configuration:

The documentation assumes the utilities curl and awk to be installed (Mac OS: brew install curl, Ubuntu: sudo apt-get install curl).

IAS Tokens

Using X.509 Client Certificate

  1. Store the certificate and key from your service configuration in separate files in PEM format.

    ⚠️ In case you experience invalid PEM file errors, \n characters might have to be replaced by newlines \n to have the PEM in the correct format.

    awk '{gsub(/\\n/,"\n")}1' <file>.pem

  2. Fetch the token using:

    curl --cert certificate.pem --key key.pem \
-X POST <<credentials.url>>/oauth2/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<<credentials.clientid>>' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'username=<<name of requesting user>>' \
--data-urlencode 'password=<<password of requesting user>>'

    ❕ Replace the <<>> placeholders with values from the service configuration and user credentials.

Using Client Credentials
  1. Fetch the token using: 
    curl -u '<<credentials.clientid>>:<<credentials.clientsecret>>' \
-X POST <<credentials.url>>/oauth2/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'username=<<name of requesting user>>' \
--data-urlencode 'password=<<password of requesting user>>'
    ❕ Replace the <<>> placeholders with values from the service configuration and user credentials.

XSUAA Tokens

Using X.509 Client Certificate
  1. Store the certificate and key from your service configuration in separate files in PEM format.

    ⚠️ In case you experience invalid PEM file errors, \n characters might have to be replaced by newlines \n to have the PEM in the correct format.

    awk '{gsub(/\\n/,"\n")}1' <file>.pem
  2. Fetch the token using: 
    curl --cert certificate.pem --key key.pem \
-X POST <<credentials.certurl>>/oauth/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<<credentials.clientid>>' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'username=<<name of requesting user>>' \
--data-urlencode 'password=<<password of requesting user>>'
    ❕ Replace the <<>> placeholders with values from the service configuration and user credentials.
Using Client Credentials
  1. Fetch the token using: 
    curl \
-X POST <<credentials.url>>/oauth/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<<credentials.clientid>>' \
--data-urlencode 'client_secret=<<credentials.clientsecret>>' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'username=<<name of requesting user>>' \
--data-urlencode 'password=<<password of requesting user>>'
    ❕ Replace the <<>> placeholders with values from the service configuration and user credentials.