Completed
Digging into why the authenticated request for an access token failed: lack of URL encoding of the values
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Back to Basics - Using Curl in the SAP Enterprise Landscape
Automatically move to the next video in the Classroom when playback concludes
- 1 Welcome and introduction
- 2 Off to the SAP Business API Hub to look at the task in hand
- 3 Examining the Service Manager API
- 4 Looking at the SAP Help Portal docu on how to get an access token and authenticate the calls
- 5 Considering the two OAuth 2.0 flows in use
- 6 Realising I'm an idiot and had completely missed the content-type header in my quiz question
- 7 Examining the docu's curl sample to retrieve a token
- 8 Exploring curl's help features
- 9 Considering HTTP POST and curl's many facilities for that
- 10 A short digression into getting curl to follow redirects with --location, and an examination of --verbose output
- 11 Looking at a more comfortable way to express x-www-form-urlencoded name/value pairs with multiple --data parameters
- 12 Digging into why the authenticated request for an access token failed: lack of URL encoding of the values
- 13 Examining the --data-urlencode parameter option, as opposed to --data
- 14 Comparing --include show the response headers with --verbose
- 15 Celebrating the receipt of an access token
- 16 Trying out a deliberately over-simplified curl request without authentication
- 17 Adding, with the --header parameter, a specific Authorization header
- 18 Comparing that with the use of --user which generates an Authorization header with some Base64 encoded string for a Basic authentication header automatically
- 19 A successfully authenticated call to the /v1/service_offerings endpoint
- 20 Avoiding curl's progress indicators with --silent
- 21 Getting ready to create a service instance with a POST request and a file-based payload with the @ mechanism of curl's --data parameter
- 22 'Useless use of cat' award from shellcheck, hurray!
- 23 Examining why we received an error "unsupported media type"
- 24 An unexpected but always welcome WhatsApp call from my son Joseph
- 25 Fixing the call with another --header parameter to specify that the Content-Type is of the payload I'm sending is application/json curl sends application/x-www-form-urlencoded by default
- 26 Getting a lovely HTTP 201 CREATED response altho the Location header is missing and checking the result with ijq and also the btp CLI
- 27 Finally, using curl to delete the instance with the --request DELETE parameter
