Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to perform a password reset for existing PKS API user in Enterprise PKS (76914)

Last Updated: 1/23/2020Categories: How toTotal Views: 3321Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides steps to reset the password for an existing Enterprise PKS API user.

Resolution

Login to the PKS client VM where the UAA cli can be run.

Issue a command similar to the following to connect to UAA on the PKS VM:

uaac target https://<PKS-API-hostname[FQDN]>:8443 --skip-ssl-validation

Retrieve the UAA admin password from Ops Manager via the Enterprise PKS Tile → Credentials page, click on the Link to Credential link next to Pks Uaa Management Admin Client, copy the value next to "secret":

Issue a command similar to the following to authenticate and obtain an access token for theadmin client from the UAA server.

uaac token client get admin -s <Pks Uaa Management Admin Client secret from Step 3>

Issue the uaac contexts command to display the users and applications authorized by UAA on the PKS VM, and the permissions granted to each user and application:

Note: You will see output similar to the following:

[0]*[https://pks.corp.local:8443]
ca_cert: /home/ubuntu/root_ca_certificate

[0]*[admin]
client_id: admin
access_token: eyJhbGciOiJSUzI1NiIsImprdSI6Imh0dHBzOi8vcGtzLmNvcnAubG9jYWw6ODQ0My90b2tlbl9rZXlzIiwia2lkIjoia2V5LTEiLCJ0eXAiOiJKV1QifQ.eyJqdGkiOiJiOTIxYWUzODhlMTQ0YjUzYjg2Y2VhODdiZDllYzcyZCIsInN1YiI6ImFkbWluIiwiYXV0aG9yaXRpZXMiOlsiY2xpZW50cy5yZWFkIiwicGtzLmNsdXN0ZXJzLmFkbWluLnJlYWQiLCJjbGllbnRzLnNlY3JldCIsInBrcy5jbHVzdGVycy5tYW5hZ2UiLCJjbGllbnRzLndyaXRlIiwidWFhLmFkbWluIiwiY2xpZW50cy5hZG1pbiIsInNjaW0ud3JpdGUiLCJwa3MuY2x1c3RlcnMuYWRtaW4iLCJzY2ltLnJlYWQiXSwic2NvcGUiOlsiY2xpZW50cy5yZWFkIiwicGtzLmNsdXN0ZXJzLmFkbWluLnJlYWQiLCJjbGllbnRzLnNlY3JldCIsInBrcy5jbHVzdGVycy5tYW5hZ2UiLCJjbGllbnRzLndyaXRlIiwidWFhLmFkbWluIiwiY2xpZW50cy5hZG1pbiIsInNjaW0ud3JpdGUiLCJwa3MuY2x1c3RlcnMuYWRtaW4iLCJzY2ltLnJlYWQiXSwiY2xpZW50X2lkIjoiYWRtaW4iLCJjaWQiOiJhZG1pbiIsImF6cCI6ImFkbWluIiwiZ3JhbnRfdHlwZSI6ImNsaWVudF9jcmVkZW50aWFscyIsInJldl9zaWciOiIxN2ZjOGRkNCIsImlhdCI6MTU3OTc0NjQ0OSwiZXhwIjoxNTc5Nzg5NjQ5LCJpc3MiOiJodHRwczovL3Brcy5jb3JwLmxvY2FsOjg0NDMvb2F1dGgvdG9rZW4iLCJ6aWQiOiJ1YWEiLCJhdWQiOlsic2NpbSIsImNsaWVudHMiLCJ1YWEiLCJhZG1pbiIsInBrcy5jbHVzdGVycy5hZG1pbiIsInBrcy5jbHVzdGVycyJdfQ.oOYi5bSVxYQeP7FhMvzNBCjoPVxjgMJwSQ4oOnNXc9SOKHPfULqWk5oqCjlMQLSfyZ-Co3j0NzKG9grGSrwnuv-rydkEqc5bM2RUP-273-tqHRDUSN4pvqOqIhgWNplZ889BHnjF5KmkicbC2zfzobF3-aBw4QSFMygaQhEzOlLjdjaK8HapXMaMI9YV7EAqmOPxNeD6Z-rGz4jPqk1Ea5flaWjEz1Rn6cQP-NirupAlJS9Oc1-wAioad3yQwpziyXGCX8M7JzqT2helJjYGJU8_g1CZ4ZGV0naM8s4L2gze2scY02eSRayahKaa5vw-9Kl4Q5tkHyy4AjwTx9oN6A
token_type: bearer
expires_in: 43199
scope: clients.read pks.clusters.admin.read clients.secret pks.clusters.manage clients.write uaa.admin clients.admin scim.write pks.clusters.admin password.write scim.read
jti: b921ae388e144b53b86cea87bd9ec72d

Note: In the output search in the scope section of the client_id: admin user for password.write. The value password.write represents sufficient permissions to change passwords.

If the admin user lacks permissions to change passwords, add the permissions by following Steps 7-9. Otherwise, skip to step 10.

Issue a commands similar to the following to add the password.write privilege:

uaac client update admin --scope "EXISTING-PERMISSIONS password.write"
uaac client update admin --authorities "EXISTING-PERMISSIONS password.write"

Note: Replace EXISTING-PERMISSIONS with the current contents of the scope section from uaac contexts (from Step 5).

Issue the following command to delete the local token:

uaac token delete

Issue a command similar to the following to obtain an updated access token from the UAA (repeat Step 4):

uaac token client get admin -s <Pks Uaa Management Admin Client secret from Step 3>

Issue a command similar to the following to change an existing user's password:

uaac password set <username> -p <new_password>

Related Information

Creating and Managing Users with the UAA CLI (UAAC) https://docs.pivotal.io/platform/application-service/2-7/uaa/uaa-user-management.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
"Error en la invocación de la comprobación de la suma de comprobación del método" durante la revisión de VCSA 6.7 U2 / U2a (70837)

KB
•
配置出站电子邮件服务器时，您会收到消息“测试连接失败 (Test connection failed)” (76868)

KB
•
vRealize Log Insight 4.x 以降での vApp プロパティのリストア (76944)

KB
•
在 vCloud Director 的 HTML5 UI 中，尝试打开“任务”列表的第 10 页时，出现“不支持的查询: adminTask0 (Unsupported query: adminTask0)”错误 (76972)

KB
•
"Erro na verificação da checksum de invocação de método" ao corrigir o VCSA 6.7 U2/U2a (70837)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant