Initial Hub configuration

You can now log in for the first time and carry out some system-wide configuration.

When you open the login page for Authentication Server, localization settings are automatically applied from your web browser. The login page and Hub display in the language most compatible with the language settings configured in the browser. If the language selected in your browser settings is not supported, English is used as the default. If required, you can manually change the language you want to use from the drop‑down list on the login page.

To watch the Hub installation and configuration process, see our Blue Prism Hub installation video.

  1. Launch a browser and go to the Authentication Server website, in our example: https://authentication.local

  2. Log in using the default credentials.

    • Username: admin
    • Password: Qq1234!!
  3. Click Hub to launch the Hub website.

  4. Change the default password to a new secure password.
    1. In Hub, click the profile icon to open the Settings page, and then click Profile.
    2. Click Update password.

      The Update your password dialog displays.

    3. Enter the current admin password, then enter and repeat a new password.
    4. Click Update.

      The admin password is changed.

Database settings

To configure access to the Blue Prism database:

  1. Click your profile icon to open the Settings page, and then click Environment manager.

    The Environment management page displays.

  2. Click Add connection and enter the details of the Blue Prism database. An example is shown below:

    The Timeout value is in seconds.

  3. Click Add connection to save the details.

    The connection is created and displays in the Environment manager.

  4. In the Environment manager, click the refresh icon on your new connection. This updates the information in Hub with the digital workforce and queues held in the database.

    If the connection is successful, the following message displays in the top right corner of the Hub user interface, which verifies the installation.

    If the message does not display, see Troubleshoot a Hub installation for more information.

Create an administrator

You will need to create an administrator account with valid information to finish the Hub configuration. You should not use the generic admin account to complete the configuration, this is because:

  • A real email address is needed in order to test the email configuration.
  • For a complete audit trail, a named user should be used to make configuration changes, rather than the generic account.

To create a new administrator:

  1. Click your profile icon to open the Settings page, and then click Users.
  2. On the Users page, click Add user.

    The Create user section displays.

  3. Enter the following details:
    • Username
    • First name
    • Last name
    • Email address

  4. Select the Hub and Hub Administrator permissions.

  5. Click Create user.

    The Create password dialog displays.

  6. Select Manually update the user’s password.

    Passwords must obey the restrictions within Hub.

  7. Click Continue and follow the instructions on screen.
  8. Finally, click Create to create the user.

    The new user displays in the list of users.

  9. Log out of Hub and log back in using your new account.

Authentication settings

Authentication settings for a Hub environment can be configured on the Authentication settings page.

To configure the authentication settings:

  1. Click your profile icon to open the Settings page, and then click Authentication settings.

    The Authentication settings page displays.

  2. Select the authentication type(s) you want to use, and the associated options if required.

    • Native authentication – This is enabled by default in new environments or when upgrading Hub.
    • Active Directory authentication – This can only be enabled if the server hosting Authentication Server is a member of an Active Directory domain. If enabled, Active Directory domains and user role management can also be configured.
    • LDAP – To enable LDAP authentication at least one LDAP connection must be created.

Based on your organization’s requirements, you have the following options:

  • Enable all authentication types.
  • Disable native authentication if there is at least one Hub administrator in the system who can sign in via LDAP or Active Directory authentication.
  • Disable both native and Active Directory authentication if there is at least one Hub administrator in the system who can sign in via LDAP.
  • If there are no LDAP users in the system, either native or Active Directory authentication must be enabled, and at least one Hub administrator configured to use the enabled authentication type must be kept in the system. A warning displays if there is no administrator configured to sign in via the currently enabled authentication type(s).

For more information about configuring authentication settings, see the Hub Administrator Guide.

Email settings

It is recommended that the SMTP setup is completed. This enables system emails to be sent, such as forgotten password emails.

The email address used to send emails is configured when setting up your profile.

To configure the email settings, you must log in with the user you created in Create an administrator. This is because the configuration process sends a test email, and therefore requires a user with an active email address.

You can configure your email settings using one of the following authentication methods:

  • Username and password – This authentication method requires the following information:
    • SMTP host
    • Port
    • Sender email
    • Encryption method
    • Username
    • Password
    • Email address to receive a test email – this defaults to the email address of the user who is making the changes.
  • Microsoft OAuth 2.0 – This authentication method requires the following information:
    • Sender email
    • Application ID
    • Directory ID
    • Client secret
    • Email address to receive a test email – this defaults to the email address of the user who is making the changes.

To configure the email settings:

  1. Click your profile icon to open the Settings page, and then click Email configuration.
  2. Click Edit.
  3. Select the authentication type you want to use.

    The fields on the page depend upon your selection as detailed above. If you select:

    • Username and password, the Email configuration page displays as follows:

    • Microsoft OAuth 2.0, the Email configuration page displays as follows:

  4. Enter the required information.
  5. Click Save.

If the email settings cannot be successfully configured, it is likely that the Message Broker server cannot be reached, see Troubleshoot a Hub installation for more information.

For more information about configuring email settings, see Hub Administrator Guide.

Configure Authentication Server

For use with versions of Blue Prism 6, Authentication Server cannot be used to authenticate users between Blue Prism and Hub. Users cannot be mapped from this version of Blue Prism. Users can log into Blue Prism and Authentication Server using independent accounts. No additional configuration is needed.

For use with Blue Prism 7.0 or later, Authentication Server can be used to map users between Blue Prism and Hub, enabling them to use the same credentials to log into both. To configure the Authentication Server, see the Authentication Server configuration guide.

To watch this installation step, see our Configure Authentication Server video.

Install Plugins

As part of the installation, Hub automatically installs the Hub plugins. However, if you want to use ALM or Interact, you will need to install the freely available Business processes plugin first.

To watch this installation step, see our Business Processes plugin installation video.

  1. Log in to Hub.
  2. Click Plugins to open the plugin repository.

  3. Click Automation lifecycle.

    The available plugin components display.

  4. Click the download icon in the bottom corner of the Business processes tile to initiate the install.

    The site restarts.