VMware Cloud Director has a brand new characteristic added in 10.4.1 launch which offers flexibility to vary Id Suppliers as per your selection and comfort, with out dropping the sources assigned to the customers. VMware Cloud Director helps Light-weight Listing Entry Protocol (LDAP), Safety Assertion Markup Language (SAML) and OpenId Join (OIDC) protocols for authentication. You may swap between these protocols or migrate to a distinct identification supplier with ease by remapping current customers to their identification in one other Id Supplier. This weblog demonstrates methods to use the consumer administration API to perform this.
Moreover, VMware Cloud Director has introduced the deprecation of help for native customers beginning with 10.4.1 launch (launch notes). VMware Cloud Director’s industry-compliant integrations with exterior Id Suppliers provides advantages of most fashionable and safe authentication schemes to its prospects. Clients can avail all of the options equivalent to Two Issue Authentication/Multi Issue Authentication, biometric integrations, good card integrations, and so on. with VMware Cloud Director. It additionally aids prospects staying updated with all future developments in authentication applied sciences.
Following is an instance to remap supplier (native) consumer to a SAML identification supplier federation. As of VMware Cloud Director 10.4.1, remapping a consumer is on the market solely as an API characteristic. Thus, for all subsequent steps use an API shopper of your selection. In my examples beneath, I’m utilizing Postman to carry out remapping.
Pre-requisite: Ensure the Id Supplier federation to which you wish to remap consumer to is precisely configured.
- Login to VMware Cloud Director as an administrator (tenant or system administrator) and determine the consumer you wish to remap. Right here, the consumer I’m remapping is ‘demouser’. This consumer is an area consumer.
- Login utilizing the API because the administrator; both utilizing their credentials (native or LDAP), IDP issued tokens (SAML or OAuth) or VMware Cloud Director’s API Token.
API: POST “https”//{api_host}/cloudapi/1.0.0/classes”
- Retrieve the urn id of ‘demouser’ from question customers API.
API: GET “https://{api_host}/cloudapi/1.0.0/customers”
Now, utilizing this urn id, fetch full data of the consumer. Seek advice from Get Person for extra perception on this API.
API: GET “https://{api_host}/cloudapi/1.0.0/customers/urn:vcloud:consumer:bafe9a31-1810-4108-8754-3ece52a4e963”
- Copy full data of the consumer from earlier step and edit following properties to be used as physique of the next PUT request.
- Replace the ‘username’ to mirror the consumer’s username within the new Id Supplier. Whereas this instance reveals a definite username getting used, it’s attainable to have less complicated updates like switching from username to e mail deal with, and so on.
- Replace the ‘providerType’ based mostly on the kind of new Id Supplier. New values of ‘providerType’ may very well be OIDC, SAML, LOCAL, LDAP.
Ship PUT request for the consumer to be remapped. Seek advice from replace consumer for extra perception on this API.
API: PUT “https://{api_host}/cloudapi/1.0.0/customers/urn:vcloud:consumer:bafe9a31-1810-4108-8754-3ece52a4e963”
The consumer ‘demouser’ has now been remapped to the tenant’s SAML identification supplier and their username has been remapped to ‘demouser@supplier.com’.
Customers will be remapped from one IDP federation to a different utilizing the identical course of. In case you are remapping a consumer to ‘LOCAL’ supplier kind, along with updating the supplier kind replace password within the physique of PUT request.
In subsequent a part of this weblog sequence, we are going to remap a tenant consumer.
Take a look at all the newest enhancements in VMware Cloud Director 10.4.
