[ vrslcm authentication base64 ]

vRSLCM API Authentication

To begin working with vRealize Suite Lifecycle Manager (vRSLCM) to leverage the api, we first need to to authenticate.

Many VMware KBs advise the following for creating the <token> The Base64 encoded value of ‘username:password’. In this example we use the default username ‘[email protected]’, and password.

While the words make sense, lets explore how one might Base64 encode the value of ‘username:password’

I tend to leverage sites like base64encode.org to accomplish quick conversion task’s.

For example lets encode: username: [email protected] password: VMwareRocks

This would form the string to encode: [email protected]:VMwareRocks

Encoding the string results in the following value: YWRtaW5AbG9jYWw6Vk13YXJlUm9ja3M=

Base64Encode.org the vRSLCM password

Updating the <token> with our base64 encoded value, we can now discover our environment details with the following curl command:

[email protected]:~$ curl -h "Authorization: Basic <token>" -k https://lcm81.corp.com/lcm/lcops/api/environments
[email protected]:~$ curl -h "Authorization: Basic YWRtaW5AbG9jYWw6Vk13YXJlUm9ja3M=" -k https://lcm81.corp.com/lcm/lcops/api/environments


DISCLAIMER This is a personal blog. Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated. Any views or opinions are not intended to malign any religion, ethnic group, club, organization, company, or individual.
All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information.
Photos
Unless stated, all photos are the work of the blog owner and are licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. If used with watermark, no need to credit to the blog owner. For any edit to photos, including cropping, please contact me first.
Recipes
Unless stated, all recipes are the work of the blog owner and are licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. Please credit all recipes to the blog owner and link back to the original blog post.
Downloadable Files
Any downloadable file, including but not limited to pdfs, docs, jpegs, pngs, is provided at the user’s own risk. The owner will not be liable for any losses, injuries, or damages resulting from a corrupted or damaged file.
Comments
Comments are welcome. However, the blog owner reserves the right to edit or delete any comments submitted to this blog without notice due to
– Comments deemed to be spam or questionable spam
– Comments including profanity
– Comments containing language or concepts that could be deemed offensive
– Comments containing hate speech, credible threats, or direct attacks on an individual or group
The blog owner is not responsible for the content in comments.
This policy is subject to change at anytime. disclamer c/o http://kaloferov.com/