Connect can be configured to use Windows Authentication for user sign on. Connect retrieves user information from Active Directory to create the Connect user identity. The user can then sign on without having to provide credentials. When Windows Authentication is enabled, users can still choose to log in using their Alteryx Connect credentials.
Windows Authentication supports both NTLM and Kerberos protocols.
If the server with Alteryx Connect service is trusted by user's browser, either with an https connection or the server is whitelisted, the user's identity is automatically passed to Alteryx Connect and the user does not have to provide credentials. Otherwise, a dialog window requiring username and password displays.
Enter credentials and press Sign in to perform authentication. If authentication fails, the Connect Sign In page displays. If the user selects Cancel, the connect is closed and a blank page displays. Access the page directly by visiting:
User credentials are created by:
An administrator - users have an email associated to their Connect account and a configured password. Administrators can also assign usernames.
The user during sign up - users have an email associated to their Connect account and a configured password.
Windows authentication - Users have an email associated to their Connect account.
If Active directory is not available or cannot be reached, the Connect sign-on page displays. Use this page to manually enter credentials. If a password is not associated with the Connect account or if users forgot their credentials, use Forgot your password? to access a link to create a new password. A defined SMTP server is necessary to use Forgot your password?.
Access Connect as a Different User
To sign in as a different user:
- Log out from the user menu.
- Use the Connect sign on page to manually access a different user account.
To update Windows Authentication to a new user:
- Verify that the previous user is logged out.
- Visit a Connect page. The authentication update should occur automatically.
Incompatible Environment Set Up
Windows Authentication is bound to HTTP protocol; therefore, if HTTP protocol fails in your environment, Windows Authentication also fails. Use the Connect sign-on page.