.. _log-in-to-admin-portal:

Log in 
----------

.. _21.4|EKB-13287:
.. _21.4-PB3|EKB-16919:
.. _21.4-PB4|EKB-17941:
.. _24.1|EKB-14835:


Overview 
..........

Starting with Automate 24.1, "classic" admin portal view of the Automate GUI has been deprecated. On install 
or upgrade, the default view of the portal is set to the newer ``admin`` portal. 


You can use the following URLs to log in: 

* ``https://{hostname}/``
* ``https://{hostname}/portal/``

.. important::

   * The trailing forward slash ``/`` is required in the URL after ``portal/``. 
   * Support is available for additional paths in the URL, for example, for use in a proxy path. 
     The supported format is as follows:  ``https://{hostname}/{some}/{custom}/{path}/portal/``
   * Users with a business admin role can use the URL, ``https://{hostname}/business-admin/``, but this 
     will *always* redirect to ``https://{hostname}/portal/``. 


.. rubric:: Related Topics 

* :ref:`introduction-to-the-admin-gui`
* :ref:`change-your-own-password`




Log in for Standard Users
..........................

To log in as a standard user: 

1. Go to either of: 

   * ``https://{hostname}/login``
   * ``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. 




Log in for LDAP Users
..........................

To log in as an LDAP user: 

#. Go to either of: 

   * ``https://{hostname}/login``
   * ``https://{hostname}/portal/login``

#. 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 :ref:`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.



Log in for SSO Users
........................


To log in as SSO user: 

#. Go to either of:  
   
   * ``https://{host name}/sso/{SSO login URI}/login``
   * ``https://{hostname}/portal/sso/{SSO login URI}/login``

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

   The SSO URLs provided redirect to the Admin portal with endpoint: ``/portal/``.



.. rubric:: Related Topics


* 
  .. raw:: latex

     SSO Users and Login in the Core Feature Guide

  .. raw:: html
  
     <a href="data-c_concepts-sso-users-and-login.html">SSO Users and Login</a>

* 
  .. raw:: latex

     LDAP Users and Login in the Core Feature Guide

  .. raw:: html
  
     <a href="data-c_concepts-ldap-users-and-login.html">LDAP Users and Login</a>