Highlighted
Enthusiast
Enthusiast

Server.searchLdapUsers returns empty

We are using VRA 7.3 and writing some workflows. We are using 'User interaction' to halt the workflow till the user logs in the VRA portal and accepts.

In one of the environment, the function Server.searchLdapUsers(name, 0) returns valid values and the user is able to see the request in Manual Action.

But in another environment, the function is returning empty.

Question is, under what conditions/scenarios will the Server.searchLdapUsers function return empty. These are indeed valid values. The same name we get

values for function Server.findAllForType('AD:User', name); But we can't use the result as the 'User interaction' expects Array/LdapUser and we can't find a

way to convert the output of AD.User to LdapUser.

Any help is much appreciated. Thanks

0 Kudos
4 Replies
Highlighted
VMware Employee
VMware Employee

Hi,

To convert from AD:User to LdapUser, you can try something like:

var ldapUser = Server.getLdapElement(adUser.distinguishedName);

Highlighted
Enthusiast
Enthusiast

Thanks.

But it didn't work.

Server.getLdapElement(dn) returns null.

I think some setup is missing. If getLdapElement works, then the searchLdapUsers() will also work.

Any idea what I am missing in the configuration of VRO?

0 Kudos
Highlighted
VMware Employee
VMware Employee

What authentication provider is configured on both vRO (LDAP, vSphere , OAuth ... ?)

Highlighted
Enthusiast
Enthusiast

Things started working after we changed the default tenant. Thanks.

But something else is happening. I see double requests in the 'Manual User Action' in the Inbox. Smiley Sad

0 Kudos