Pivotal/UAA
From r00tedvw.com wiki
(Difference between revisions)
(Created page with "[[Pivotal/UAA|UAA] =Installing Ruby on Mac OSX= Use Homebrew <nowiki>~$ brew install rbenv ~$ eval "$(rbenv init -)" ~$ rbenv install 2.5.1 </nowiki> =Connecting to UAA serve...") |
|||
| Line 1: | Line 1: | ||
| − | [[Pivotal/UAA|UAA] | + | [[Pivotal/UAA|UAA]] |
| − | =Installing Ruby on Mac OSX= | + | =UAAC CLI= |
| + | ==Installing Ruby on Mac OSX== | ||
Use Homebrew | Use Homebrew | ||
<nowiki>~$ brew install rbenv | <nowiki>~$ brew install rbenv | ||
| Line 6: | Line 7: | ||
~$ rbenv install 2.5.1 | ~$ rbenv install 2.5.1 | ||
</nowiki> | </nowiki> | ||
| + | ==Install UAAC CLI== | ||
| + | <nowiki>~$ sudo gem install cf-uaac</nowiki> | ||
=Connecting to UAA server= | =Connecting to UAA server= | ||
use the <code>uaac target uaa.<system domain></code> command to target the UAA server. | use the <code>uaac target uaa.<system domain></code> command to target the UAA server. | ||
| Line 14: | Line 17: | ||
<nowiki>OPs Manager > PAS > Credentials > UAA > Admin Client Credentials</nowiki> | <nowiki>OPs Manager > PAS > Credentials > UAA > Admin Client Credentials</nowiki> | ||
With that information, we can use <code>uaac token client get admin -s ADMIN-CLIENT-SECRET | With that information, we can use <code>uaac token client get admin -s ADMIN-CLIENT-SECRET | ||
| + | =Quick Reference= | ||
| + | ==uaac contexts== | ||
| + | Displays the users and applications authorized by the UAA server, along with the permissions granted. | ||
| + | <nowiki>~$ uaac contexts</nowiki> | ||
Revision as of 15:16, 3 August 2018
UAA
Contents |
UAAC CLI
Installing Ruby on Mac OSX
Use Homebrew
~$ brew install rbenv ~$ eval "$(rbenv init -)" ~$ rbenv install 2.5.1
Install UAAC CLI
~$ sudo gem install cf-uaac
Connecting to UAA server
use the uaac target uaa.<system domain> command to target the UAA server.
ie. ~$ uaac target uaa.run-16.haas-59.pez.pivotal.io
next, we need to authenticate and obtain an access token. Record the uaa:admin:client_secret from your deployment manifest (stored in ~/.uaac.yml
OR, if you are using a vcenter deployment, obtain it by:
OPs Manager > PAS > Credentials > UAA > Admin Client Credentials
With that information, we can use uaac token client get admin -s ADMIN-CLIENT-SECRET
Quick Reference
uaac contexts
Displays the users and applications authorized by the UAA server, along with the permissions granted.
~$ uaac contexts
