Unable to login to the platform using SSO

News Knowledge Base
1

After the AS upgrade, why doesn't the login to the platform using SSO work?

Issue Description :

After the AS upgrade, unable to log in to the platform using SSO.

Resolution:

The first thing to do is check the configurations per our documentation:

https://docs.uipath.com/automation-suite/automation-suite/2023.4/installation-guide/setting-up-kerberos-authentication

After upgrading Automation Suite to version 2023.10.4, it is recommended to review the cluster_config.json file, and in a scenario, we noticed that the details under the Kerberos section were missing.

Steps to Follow to Update the Kerberos Settings:

  1. Review the Cluster Configuration:

    We navigated to the following location:

    cat /opt/UiPathAutomationSuite/latest/cluster_config.json

    to verify whether the Kerberos details were present in the newly created cluster configuration.
    If the details were missing, we referred to the previous (older) cluster configuration and manually added the required Kerberos entries, such as:


    "kerberos_auth_config": {
    "enabled": true, "ticket_lifetime_in_hour": 8,
    "ad_domain": "xxxxxx",
    "default_ad_username": "xxxxx",
    "default_user_keytab": "xxxxxx"
    }

  2. Run the Installer Script:

    After updating the configuration, we executed the following command to apply the changes:

    ./install-uipath.sh -i cluster_config.json -o output.json -f -s --install-type offline --accept-license-agreement

  3. Update the Password in Orchestrator:

    Once the script executed successfully, we logged in as an admin to the Orchestrator web interface, selected the appropriate tenant, and updated the password under the Security tab