Pivotal/UAA - Revision history

R00t: /* Authenticating with UAA for cf api */

2018-09-06T20:58:19Z

‎Authenticating with UAA for cf api

2018-09-06T20:16:17Z

‎Authenticating with UAA for ops man api

2018-09-06T20:15:47Z

‎Authenticating with UAA for uaa api

2018-09-06T19:54:40Z

2018-09-06T19:38:13Z

2018-09-06T18:50:15Z

2018-09-06T18:24:08Z

2018-09-06T18:21:20Z

2018-08-21T14:54:13Z

‎Quick Reference

2018-08-20T20:20:30Z

‎Connecting to UAA server

@@ Line 79: / Line 79: @@
 ===Authenticating with UAA for cf api===
-  <nowiki>~$ uaac target uaa.run-10.haas-10.pez.pivotal.io
+  <nowiki>~$ uaac target uaa.run-10.haas-59.pez.pivotal.io
 ~$ uaac token owner get
 Client ID: cf

@@ Line 62: / Line 62: @@
 ===Authenticating with UAA for ops man api===
   <nowiki>~$ uaac target opsmgr-10.haas-59.pez.pivotal.io/uaa
 ~$ uaac target owner get

@@ Line 86: / Line 86: @@
 ===Authenticating with UAA for uaa api===
   <nowiki>~$ uaac target uaa.run-10.haas-59.pez.pivotal.io
 ~$ uaac token client get admin -s {password from PAS > UAA > Admin Client Credentials}</nowiki>

@@ Line 60: / Line 60: @@
 This api target provides access to:
 * the Ops Man API token, users, and scopes
 ==Pivotal Application Service (PAS)==
@@ Line 68: / Line 76: @@
 * the CF API token, users, and scopes
 * creating users and scopes for apps manager
 ==Pivotal Container Service (PKS)==
 ==Concourse==

@@ Line 58: / Line 58: @@
   <nowiki>https://{ops-manager-fqdn}/uaa
 ie. https://opsmgr-10.haas-59.pez.pivotal.io/uaa</nowiki>
-This api target provides access to the Ops Man API token, users, and scopes
+This api target provides access to:
 ==Pivotal Application Service (PAS)==
@@ Line 64: / Line 65: @@
   <nowiki>https://uaa.{system_domain}
 ie. https://uaa.run-10.haas-59.pez.pivotal.io</nowiki>
-This api target provides access to the CF API token, users, and scopes
+This api target provides access to:
 ==Pivotal Container Service (PKS)==
 ==Concourse==

@@ Line 52: / Line 52: @@
   <nowiki>~$ uaac users "username eq 'username'"</nowiki>
-==Common UAA Instances==
+=Common UAA Instances=
 Below are some common instances of UAA as it pertains to Cloud Foundry installations.
-===Operations Manager (Ops Man)===
+==Operations Manager (Ops Man)==
-===Pivotal Application Service (PAS)===
+==Pivotal Application Service (PAS)==
-===Pivotal Container Service (PKS)===
+==Pivotal Container Service (PKS)==
-===Concourse===
+==Concourse==

← Older revision		Revision as of 18:21, 6 September 2018
Line 51:		Line 51:
	===locate specific user based on username===		===locate specific user based on username===
	<nowiki>~$ uaac users "username eq 'username'"</nowiki>		<nowiki>~$ uaac users "username eq 'username'"</nowiki>
		+
		+	==Common UAA Instances==
		+	Below are some common instances of UAA as it pertains to Cloud Foundry installations.
		+	===Operations Manager (Ops Man)===
		+	===Pivotal Application Service (PAS)===
		+	===Pivotal Container Service (PKS)===
		+	===Concourse===

@@ Line 39: / Line 39: @@
 =Quick Reference=
 ==uaac contexts==
 Displays the users and applications authorized by the UAA server, along with the permissions granted, within the current scope.

@@ Line 19: / Line 19: @@
 With that information, we can use
   <nowiki>~$ uaac token client get admin -s ADMIN-CLIENT-SECRET</nowiki><br \>
-If the above doesn't work, try decrypting the installation yml file.  SSH into the ops manager and then run these with the admin passcode:
+<br \>If the above doesn't work, try decrypting the installation yml file.  SSH into the ops manager and then run these with the admin passcode:
   <nowiki>~$ sudo -u tempest-web RAILS_ENV=production /home/tempest-web/tempest/web/scripts/decrypt /var/tempest/workspaces/default/actual-installation.yml /tmp/actual-installation.yml
 ~$ sudo -u tempest-web RAILS_ENV=production /home/tempest-web/tempest/web/scripts/decrypt /var/tempest/workspaces/default/installation.yml /tmp/installation.yml</nowiki>