Log In to the Admin Portal#

Overview#

The VOSS Automate system offers two portals: admin and classic.

Important

The base address URL to enable and access these portals is configurable from the system command line interface using the web portal commands on application nodes.

For details, see the Web Portal Configuration section in the Platform Guide.

Upon installation or upgrade, the classic portal is enabled and set to default. This means that the following URLs can be used to log in:

  • https://{hostname}/

  • https://{hostname}/portal-classic/ (redirects to https://{hostname}/)

If the admin portal is enabled and set to default, the following URLs can be used to log in:

  • https://{hostname}/

  • https://{hostname}/portal/

Important

The trailing forward slash / is required in the URL after portal/ in order to log in successfully.

Support is also available for extra paths in the URL, for example, for use in a proxy path. The supported format is:

https://{hostname}/{some}/{custom}/{path}/portal/

If both portals are enabled, the default portal can be accessed with:

  • https://{hostname}/

In this case, the respective portals can be accessed with:

  • https://{hostname}/portal-classic/ (redirects to https://{hostname}/)

  • https://{hostname}/portal/

Your username and password are the same.

Note

The URL: https://{hostname}/business-admin/ is still available in release 21.4 for users with a business admin role, but will always redirect to https://{hostname}/portal/, regardless of the portal that is set to be the default.

Related Topics

Standard Users#

To log in as a standard user:

  1. Go to:

    • Default: https://{hostname}/login

    • Classic: https://{hostname}/portal-classic/login (redirects to https://{hostname}/login)

    • Admin: https://{hostname}/portal/login

  2. Enter your username, using either of these formats:

    • {username}@hierarchy

    • {email address}

    • {username}

Important

If logging in with just {username}, your username must be unique at the hierarchy level, else login fails. In this case, log in using either {username}@hierarchy or {email address}. Email address must be unique in the system.

LDAP Users#

To log in as an LDAP user:

  1. Go to URL:

    • Default: https://{hostname}/login

    • Classic: https://{hostname}/portal-classic/login (redirects to https://{hostname}/login)

    • Admin: https://{hostname}/portal/login

  2. Log in, using either user ID ({user ID}[@hierarchy]), or your email address.

    • User ID ({user ID}) corresponds to the username mapping in User Field Mapping, for example, email address, user principal name, sAMaccountName. The login attribute name is configured in the authentication attribute of the LDAP device associated with the hierarchy. The authentication attribute value is obtained from the User Field Mapping, and is used to authenticate against LDAP. See User Field Mapping

    • @hierarchy is not required when the user ID corresponds to the user’s email address (regardless of the login attribute name specified in the LDAP network connection). The hierarchy is in dot notation and corresponds with the hierarchy to which the user belongs. Hierarchy level is the level at which the user is created.

SSO Users#

To log in as SSO user:

  1. Go to URL:

    • Default: https://{host name}/sso/{SSO login URI}/login

    • Classic: https://{hostname}/portal-classic/sso/{SSO login URI}/login (redirects to https://{host name}/sso/{SSO login URI}/login)

    • Admin: https://{hostname}/portal/sso/{SSO login URI}/login

  2. Log in using the relevant SSO identity provider credentials.

  • If admin is set as default portal, the SSO URLs provided redirect to the Admin portal with endpoint: /portal/.

  • If classic is set as default portal the SSO URLs for business-admin and admin log into the Admin portal.

  • If classic is set as default portal, the general (non-admin specific) SSO URL logs into the Classic portal.

See also: SSO Users and Login.

Related Topics