This Objective has below sub-objectives
· Configure the default Tenant
· Create Tenants according to a deployment plan
· Configure an Identity Store for a Tenant
· Create Tenant Roles to meet deployment requirements
· Configure the branding for the default tenant
· Configure the branding for a non-default tenant
· Set Approval Policies for different departments
The default tenant is automatically created when you configure single sign-on, which is vSphere.local
1. Login to the default tenant, https://vRA_FQDN/vcac and enter username - administrator@vsphere.local and its password
2. Click on the Tenant, vsphere.local
Each tenant requires at least one identity store. Identity stores can be OpenLDAP or Active Directory. Active Directory in native mode is supported for the default tenant only.
3. Click on identity stores and update the information. make sure the Type is set to Native Active Directory. You can use AD Explorer for Login user DN & Group search base DN. Click on Test Connection to confirm the connection and then click on Update to save the settings.
4. Click on Administrators Tab and update the Tenant and Infrastructure Administrators. Click on Update to save the changes.
Non-Default tenant branding steps are similar, If you do not configure the branding on Tenant then it would take the branding configurations from the default Tenant.
1. Login to the vRA Tenant and go to Administration > Branding
2. Uncheck the "Use Default" and Update the requested information for Header & Footer with the desired configurations and click on Update to Save. This configuration would be specific to only this Tenant.
· Configure the default Tenant
· Create Tenants according to a deployment plan
· Configure an Identity Store for a Tenant
· Create Tenant Roles to meet deployment requirements
· Configure the branding for the default tenant
· Configure the branding for a non-default tenant
· Set Approval Policies for different departments
The default tenant is automatically created when you configure single sign-on, which is vSphere.local
Configure the default Tenant / Identity Store / Roles
1. Login to the default tenant, https://vRA_FQDN/vcac and enter username - administrator@vsphere.local and its password
2. Click on the Tenant, vsphere.local
Each tenant requires at least one identity store. Identity stores can be OpenLDAP or Active Directory. Active Directory in native mode is supported for the default tenant only.
3. Click on identity stores and update the information. make sure the Type is set to Native Active Directory. You can use AD Explorer for Login user DN & Group search base DN. Click on Test Connection to confirm the connection and then click on Update to save the settings.
4. Click on Administrators Tab and update the Tenant and Infrastructure Administrators. Click on Update to save the changes.
Configure the branding for the default tenant
System administrators control the default branding for all tenants. A tenant administrator can change the branding of the portal including the logo, the background color, and the information in the header and footer. If the branding for a tenant is changed, a tenant administrator can always revert back to the system defaults.
1. Login to the default tenant, https://vRA_FQDN/vcac and enter username - administrator@vsphere.local and its password
2. Click on the Branding on the left and uncheck the "Use Default" on top. Now update the requested information
Configure the branding for a non-default tenant
Non-Default tenant branding steps are similar, If you do not configure the branding on Tenant then it would take the branding configurations from the default Tenant.
1. Login to the vRA Tenant and go to Administration > Branding
2. Uncheck the "Use Default" and Update the requested information for Header & Footer with the desired configurations and click on Update to Save. This configuration would be specific to only this Tenant.
Set Approval Policies for different departments
This topic is covered here.
No comments:
Post a Comment