Completed
Noting that the broker name begins "sm", denoting this is a broker managed by the Service Manager rather than by CF
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Digging Deeper into Service Brokering and Consumption on SAP Business Technology Platform
Automatically move to the next video in the Classroom when playback concludes
- 1 Welcome and introduction
- 2 Reviewing where we got to last time, including the registration of the service broker at the SAP Service Manager level
- 3 Now creating another service instance at the CF level and checking the OSBAPI calls
- 4 Noting that the broker name begins "sm", denoting this is a broker managed by the Service Manager rather than by CF
- 5 Deleting the service instance, again, checking the OSBAPI calls
- 6 Seeing how we can create service instances in the BTP cockpit from the service broker we've registered
- 7 Deleting that cockpit-created service instance along with another service instance I found
- 8 Starting to understand, by exploration, that SAP Service Manager operates at the *subaccount* level
- 9 Going even deeper to the SAP Service Manager APIs
- 10 Exploring the SAP Service Manager API on SAP API Business Hub, and the documentation
- 11 Relating the two types of access user and technical to their corresponding OAuth 2.0 grant types
- 12 Assigning my user the Subaccount Service Administrator role collection, via the SAP btp CLI
- 13 Building a curl invocation to request a token from the OAuth 2.0 endpoint including a quick foray into the small but useful 'bsp' script, the 'pass' utility, and URL encoding
- 14 Examining the token data
- 15 Using the token to successfully authenticate a request to one of the API endpoints!
