Follow

Buttonwood Cloud Broker Configuration

After the Cloud Broker OVA is deployed, initial configuration is required to complete the installation. 

NOTE – LDAP authentication setup requires information about your LDAP environment.  Contact your LDAP administrator for the required information.

To perform initial configuration, complete the following.

  1. Use a web browser to access the Admin Console UI at https://<ip-address-of-appliance>:8443/
  2. At the login page, enter the default credentials.  The default username is admin and the password is woodmin
  3. Once logged in, on the Home page, enter the following information.
  • Exchange Services URL – The Cloud Exchange Services URL.
  • Access Key – The Cloud Exchange Services Access Key.
  • Secret Key – The Cloud Exchange Services Secret Key.
  • New Administrator Password – The new password for the local admin account.
  • Confirm Administrator Password – Reconfirm the new password for the local admin account.  

      4. Click the  button to save the settings.  A status bar will appear confirming the initial configuration is completed. 

      5. Navigate to Broker Configuration menu and select User Authentication tab.

      6. Under Settings section, click  button.

      7. Select the checkbox as indicated in the screen below to enable LDAP configuration.  

      8. Enter the following LDAP information.


  •  LDAP Server URL:  Enter ldap://<fqdn-of-ldap-server>:<ldap-port>/

e.g. ldap://myds.example.com:389

  • LDAP Server Bind User Name:  Enter the DN for an account that is authorised to read the directory service database.

e.g. CN=myldaplookup,CN=Users,DC=example,DC=com

  • LDAP Bind Password:  Enter the password associated with the account that is authorised to read the directory service database entered in previous step.

e.g. mytestpassword

  • Search Base DN:  Enter the base DN used by LDAP Users subject in the LDAP server from which to begin the search.

e.g. OU=My Users,DC=example,DC=com

  • Group Search Base DN:  Enter the base DN used by LDAP Groups subject in the LDAP server from which to begin the search.

e.g. OU=My Groups,DC=example,DC=com

  • User Attribute Mapping:  If you are using Microsoft AD, enter userPrincipalName ={0} as the value.  If you are using other LDAP systems, obtain the correct value from your LDAP administrator.

e.g. userPrincipalName ={0}

  • Group Attribute Mapping:  If you are using Microsoft AD, enter member={0} as the value.  If you are using other LDAP systems, obtain the correct value from your LDAP administrator.

e.g. member={0}

  • Test Username (Optional):  Enter a user account to test LDAP lookup functionality.

e.g. mytestuser@example.com

 

     9. Click the button to test the settings before applying the changes.  A successful LDAP lookup should appear similar to the example screen below.  At times there might be more text include in the successful test result.  This does not constitute an error or failure.  The “OK LDAP Test completed successfully” text constitutes a successful test in all cases.

   10. Re-enter the LDAP Bind Password before applying the settings.

   11. Click the button to save the settings.

NOTE - Upon clicking on the Apply Changes button, a LDAP lookup will be carried out on the test account to verify the LDAP information entered are correct.

   12. Status bars will appear confirming configuration changes.  

   13. Navigate to Services menu, under Application section, click Restart button to restart application service.  

A status bar will display briefly while the application service is being restarted. The restart process could take up to five minutes to complete.  To monitor the Application Service Restart process, navigate to the Logs Menu.  The “INFO: Server startup in …. ms” indicates the Application Service has been successfully restarted. 

   14. Once the application service restart process is completed, use a web browser to access the Cloud Broker Login Portal at https://<ip-address-of-appliance>/

   15. At the Login Portal, log in with your AD/LDAP credentials.  

   16. The Overview page of the Cloud Broker should appear once you are successfully authenticated.

What's Next?

More

Why Buttonwood, Advantages of Buttonwood 

Log a support ticket or ask the Community

 

Was this article helpful?
0 out of 0 found this helpful

Comments