I am trying to create a vRA XaaS service that puts the user account that requested the service on a drop-down menu. This is of course part of a much larger plan. This is just testing how to get the user account data on that menu.
So, I created an action
--------------------------------------- Code ------------------------------------------------
var ans = ["fooy"];
var tenant;
var name;
try {
tenant = vCACCAFEHost.tenant;
name = System.getContext().getParameter("__asd_requestedBy");
} catch (e) {
ans = ["Exception", e];
}
ans = [ "testing", "tenant:" + tenant, "Req by:" + requestedBy, "Name:" + name, "done"];
return ans;
-----------------------------------------------------
Then I created a vRO Workflow for vRA to call
-----------------------------------------------------------------
Then create and run the XaaS blueprint.
But when I run it, All I get is
What am I missing here. How do I get the account of the user requesting this blueprint on this menu?
The entire system is vRA 6.2.2 and vRO 6.,0.3
Thanks all,
Carl L.
tenant = vCACCAFEHost.tenant;
Accepted Solutions
Carl - that's what I told you to do. You said you didn't want to change it on hundreds of blueprints.
This is where I told you to do that:
You could take the same value and wire it to RequestedBy input on the action you're already calling. It would look something like this (mapping external value parameter inputs):
So I can't remember if vRA 6.x had this in there, but you can try linking an input to the action to the PrincipalID from vRA. I have an example of this on an XaaS blueprint form which calls a vRO workflow that uses their ID to do some work. The form looks like this in vRA 7.2:
If you make a request for this item in the catalog, the form is displayed like this (the input is constrained to that value):
You could take the same value and wire it to RequestedBy input on the action you're already calling. It would look something like this (mapping external value parameter inputs):
I have several 6.x environments in my lab, but none of them are booted at the moment so I couldn't easily check to see if this was there in 6.2.2. Hopefully you could use this approach.
OK, then it must not work in 6.x because in 7, it returns the vRA user making the request. This is from an XaaS blueprint form in vRA 7.2 catalog:
The first entry on the list = Server.getCurrentLdapUser().userPrincipalName. The remaining items are built from Server.getCurrentLdapUser().allGroups, which is a list of all groups the user is a member of.
The user listed in my screenshot is the vRA logged in user, not the service account connecting to the embedded vRO server.
If I had to guess why it's different in 6 vs. 7, I would say either because of the Horizon Identitity manager integration vs. SSO identity appliance integration in 6; or if you're using an external vRO server (as was recommended in 6.x) it could be due to the authentication scheme used on the vRO server not being federated with vRA's SSO. At this point I can't remember if an external vRO 6.x appliance had an option to integrate with an SSO domain/vRA instance, so it's just a guess.
Found the answer. Thought I would put it here in case anyone else looks for how to do it.
The secret was to use the "Values" tab in vRA (not presentation in vRO) and have the action that generates the list of values take one parameter (in my case "requestedBy") and then pass the vRA principal as the value for that argument.
Carl - that's what I told you to do. You said you didn't want to change it on hundreds of blueprints.
This is where I told you to do that:
You could take the same value and wire it to RequestedBy input on the action you're already calling. It would look something like this (mapping external value parameter inputs):