- Getting started
- Introduction
- Logging in to Orchestrator
- Resetting Your Password
- Activities Feeds
- Best practices
- Tenant
- Actions
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Action Catalogs
- Profile
- System Administrator
- Identity Server
- Authentication
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
Logging in to Orchestrator
https://orchestrator_tests.com
.
You can log in to Orchestrator with:
- A user account previously created in the Users page (For more information, see the Managing Users page). Please note that on the first login, these users have to reset their password.
- A user account under a Windows Active Directory group previously added in the Users page. By default, the NTLM authentication protocol is used. To switch to Kerberos, please take a look at this page.
- A user account under a Microsoft Azure Active Directory group that was previously added in the Users page.
Logging in with the same user on a different machine or browser session disconnects the user from the first machine/session.
If external users (from the Windows or Azure AD) are members of multiple tenants, when they log in they are redirected to the Choose Tenant page.
You can also set up your environment to automatically log in to Orchestrator, on the default tenant.
If you enable AutoLogin and access an Orchestrator URL without being authenticated, the app tries to automatically log in with your current Active Directory user, without redirecting to Login page. If AutoLogin is disabled, you are redirected to the Login page. Manually press the "Windows" button to perform a Windows Login.
After 10 failed login attempts the user is locked out for 5 minutes. These are the default Account Lockout settings which can be changed on the Security tab.