Partners Blog Contacts

When a user is created manually in the VidyoPortal, there is a specific set of attributes required to create an account. The following list of Portal Attributes can be mapped based on LDAP Attributes in order to create accounts automatically.

When you provision users with LDAP, user data is read-only in the Edit User pop-up after clicking a member name from Users > Manage Users in the Admin portal.


LDAP_User_Account_Attributes_1.png

The following list explains VidyoPortal attributes (Portal Attribute Names) that can be mapped to LDAP Attribute Names. Default Values for the attributes and Value mapping selection criteria (where applicable) are also explained here.

  • User Name is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the VidyoPortal User Name in your LDAP schema.

      Many users choose to enter userPrinicpalName as the LDAP Attribute Name when using a Microsoft Active Directory LDAP server. This is a required attribute.

      The LDAP Attribute you associate with the User Name must be specified as part of your Filter template. For more information, see Configuring Your VidyoPortal Tenant to Use Your LDAP Server.

    • No Default Value is entered for User Name.

      Default Value may not be configured because this is a mandatory, unique attribute.

    • No Value mapping configurations are made for the User Name.

  • User Type is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the User Type in your LDAP schema.

      Many users choose to enter memberOf as the LDAP Attribute Name. The memberOf value returns a list of groups of which the particular user is a member. This list is then used for Value mapping selection criteria.

    • The Default Value you enter here is used as the default User Type when the LDAP Attribute Name does not exist or returns an invalid attribute value or no Value mapping criteria is met.

      You can select from Admin, Operator, Normal, VidyoRoom, Executive, and VidyoPanorama options.

    • The Value mapping is used to make specific associations between exact Portal Attribute Values and LDAP Attribute Values based on the LDAP Attribute Name selected for your User Type.

      Different users return different LDAP Attribute Values. The Attribute Values Mapping pop-up allows you to map specific associations for all possible values returned.

      If desired, select the Duplicate or Remove buttons to create or delete rows in the Attribute Values Mapping pop-up.

      The following screenshot provides an example of a Value mapping configuration where the memberOf LDAP Attribute Name is used.


LDAP_User_Account_Attributes_2.png

For example, using the screenshot shown here, you can see that when a user is a member of the VidyoAdministratorUser group and logs in to the User or Admin portal, the account is created with the Admin User Type.

In order to create these Portal User Type mapping associations, Vidyo recommends your LDAP administrator creates specific security groups on your LDAP server in advance.

 

  • Display Name is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the Display Name in your LDAP schema.

      Many users choose to enter DisplayName as the LDAP Attribute Name.

    • In the Default Value field, enter a value for the Display Name in this cell for use when a value is somehow missing for any reason.

      If you do not type a Default Value for the Display Name in this cell, the system uses the User Name as the default.

    • No Value mapping configurations are made for the Display Name.

 

  • E-Mail Address is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the Email Address in your LDAP schema.

      Many users choose to enter mail as the LDAP Attribute Name. When a user logs in to the User or Admin portal, the system validates that the LDAP Attribute Name value is actually an email address. Otherwise, the system uses the Default Value.

      The Default Value you enter here is the domain portion of the automatically created email address for the account. When a user logs in to the User or Admin portal and an invalid email address is provided as the LDAP Attribute Name, the system constructs an email address for the account by taking the User Name provided, combining it with what you type as the Default Value, and inserts an @ symbol in between them.

      For example, if you log in as jsmith and your Default Value is Vidyo.com, the system will automatically construct an email address of jsmith@vidyo.com.

    • No Value mapping configurations are made for the E-Mail Address.


  • Extension is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map the Extension in your LDAP schema.

      You may choose to enter telephoneNumber as the LDAP Attribute Name when using a Microsoft Active Directory LDAP server.

    • No Default Value is entered for Extension.

      When a user logs in to the User or Admin portal and an empty or invalid LDAP Attribute Name is retrieved from your LDAP server, the system randomly auto-generates an extension value for the new account.

      If you do not wish to map extensions for new accounts, leave the LDAP Attribute Name blank and the system will use the Default Value to randomly auto-generate extension values for new accounts. The number of digits in the auto generated extension values is not fixed and may vary.

       

    • No Value mapping configurations are made for the Extension.

  • Proxy is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the Proxy in your LDAP schema.

      Many users choose to enter memberOf as the LDAP Attribute Name. The memberOf value returns a list of groups of which the particular user is a member. This list is then used for Value mapping selection criteria.

    • The Default Value you enter here is used as the default Proxy when the LDAP Attribute Name does not exist or returns an invalid attribute value or no Value mapping criteria is met.

      The VidyoPortal tenant used in this example has Proxies configured as nj2-al-vvr1, il2-al-vvr1, nj1-al-vr1, etc. from which you can select. Map these groups using the Attribute Value Mapping pop-up.

      LDAP_2.png

    • The Value mapping is used to make specific associations between exact Portal Attribute Values and LDAP Attribute Values based on the LDAP Attribute Name selected for your Proxy.

      Different users return different LDAP Attribute Values. The Attribute Values Mapping pop-up allows you to map specific associations for all possible values returned.

      Click the Duplicate and Remove buttons to create or delete rows in the Attribute Values Mapping pop-up if desired.

      The following screenshot provides an example of a Value mapping configuration where the memberOf LDAP Attribute Name is used.

      LDAP_User_Account_Attributes_6.png

      For example, using the screenshot shown here, you can see that when a user is a member of the nj2-al-vvr1 VidyoProxy and logs in to the User or Admin portal, the account is created with the nj2-al-vvr1 VidyoProxy.

  • Group is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map the Group in your LDAP schema.Group is the name of this specific LDAP attribute in the VidyoPortal.

      Many users choose to enter memberOf as the LDAP Attribute Name. The memberOf value returns a list of groups of which the particular user is a member. This list is then used for Value mapping selection criteria.

    • The Default Value you enter here is used as the default User Type when the LDAP Attribute Name does not exist or returns an invalid attribute value or no Value mapping criteria is met.

      The VidyoPortal tenant used in this example has group configured as Default, VidyoUS_East, VidyoUS_West, etc. values from which you can select. Map these groups using the Attribute Value Mapping pop-up.

      LDAP_1.png

    • The Value mapping is used to make specific associations between exact Portal Attribute Values and LDAP Attribute Values based on the LDAP Attribute Name selected for your User Type.

      Different users return different LDAP Attribute Values. The Attribute Values Mapping pop-up allows you to map specific associations for all possible values returned.

      If desired, select the Duplicate or Remove buttons to create or delete rows in the Attribute Values Mapping pop-up.

      The following screenshot provides an example of a Value mapping configuration where the memberOf LDAP Attribute Name is used.


      LDAP_User_Account_Attributes_4.png

      For example, using the screenshot shown here, you can see that when a user is a member of the Default group and logs in to the User or Admin portal, the account is created with the Default Group.

  • Description is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map the Description in your LDAP schema.

      You may choose to enter title as the LDAP Attribute Name.

    • The Default Value you enter here is used as the default Description when the LDAP Attribute Name does not exist or returns an invalid attribute value or no Value mapping criteria is met.

    • No Value mapping configurations are made for the Description.


  • Location Tag is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value to map to the Location Tag in your LDAP schema.

      Many users choose to enter physicalDeliveryOfficeName as the LDAP Attribute Name. The physicalDeliveryOfficeNameattribute returns the user’s office location. This value is then used for Value mapping selection criteria.

    • The Default Value you enter here is used as the default Location Tag when the LDAP Attribute Name does not exist or returns an invalid attribute value or no Value mapping criteria is met.

      The VidyoPortal tenant used in this example has Location Tags configured as Default, east_us_region_tag, west_us_region_tag, etc. values from which you can select.

      LDAP_3.png

    • The Value mapping is used to make specific associations between exact Portal Attribute Values and LDAP Attribute Values based on the LDAP Attribute Name selected for your location tag.

      Different users return different LDAP Attribute Values. The Attribute Values Mapping pop-up allows you to map specific associations for all possible values returned.

      Click the Duplicate and Remove buttons to create or delete rows in the Attribute Values Mapping pop-up if desired.

      The following screenshot provides an example of a Value mapping configuration where the physicalDeliveryOfficeName LDAP Attribute Name is used.

      LDAP_User_Account_Attributes_8.png

      For example, using the screenshot shown here, you can see that when a user is a member of the Hackensack Office group and logs in to the User or Admin portal, the account is created with the EAST Location Tag.

  • The following attributes are optional biographical information about the user. Therefore, default values are not set for these attributes:
    • Phone Number 1
    • Phone Number 2
    • Phone Number 3
    • Department
    • Title
    • IM
    • Location

  • Thumbnail Photo is the name of this specific LDAP attribute in the VidyoPortal.
    • The Thumbnail Photo must be a .png, .jpg, or jpeg and smaller than the maxium size that the Super Admin configures in Settings > Feature Settings > User Attributes within the Super Admin Portal.

      For more information, see Configuring User Attributes.

    • No Default Value is entered for Thumbnail Photo.

    • No Value mapping configurations are made for Thumbnail Photo.

  • User Groups is the name of this specific LDAP attribute in the VidyoPortal.
    • In the LDAP Attribute Name field, enter a value you have decided as being the attribute you want to associate the User Group within your existing LDAP schema.

    • No Default Value is entered for User Groups.

    • No Value Mapping configurations are made for User Groups.
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Follow
Please sign in to leave a comment.