Digging Deeper into Service Brokering and Consumption on SAP Business Technology Platform

Welcome and introduction
Reviewing where we got to last time, including the registration of the service broker at the SAP Service Manager level
Now creating another service instance at the CF level and checking the OSBAPI calls
Noting that the broker name begins "sm", denoting this is a broker managed by the Service Manager rather than by CF
Deleting the service instance, again, checking the OSBAPI calls
Seeing how we can create service instances in the BTP cockpit from the service broker we've registered
Deleting that cockpit-created service instance along with another service instance I found
Starting to understand, by exploration, that SAP Service Manager operates at the *subaccount* level
Going even deeper to the SAP Service Manager APIs
Exploring the SAP Service Manager API on SAP API Business Hub, and the documentation
Relating the two types of access user and technical to their corresponding OAuth 2.0 grant types
Assigning my user the Subaccount Service Administrator role collection, via the SAP btp CLI
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
Examining the token data
Using the token to successfully authenticate a request to one of the API endpoints!