How to create a UAA client used for concourse pipelines in Operations Manager when SAML Authentication is enabled
book
Article ID: 293528
calendar_today
Updated On:
Products
Operations Manager
Environment
Cause
All of the existing custom UAA client will be deleted after switching from internal authentication to SAML authentication. This procedure is helps Operations recreate custom clients with require scopes. For more information on what scopes to choose from see https://docs.pivotal.io/pivotalcf/2-2/opsguide/config-rbac.html#about
Resolution
Obtain the opsman client security token using a SAML user that is a member of the SAML group mapped as the Operations manager Administrator. This SAML group was configured in the page https://opsmgr.pivotal.io/saml_identity_provider/new.
Just press enter when prompted for "Client secret:". No secret required.
Get your new access token from "uaac context" and set it to the environment variable $TOKEN
export TOKEN="xxxx"
(Optional) Execute apply changes as per the below example or submit a less intrusive GET request to /api/v0/deployed/products. For a complete API reference navigate to the docs endpoint in your existing Operation Manger at https://opsmgr.pivotal.io/docs
curl -vvv -H "Authorization: Bearer $TOKEN" -k https://opsmgr.pivotal.io/api/v0/installations -X POST