How does EasySSO work with User Directories backed up by Active Directory?

When an Atlassian application has EasySSO deployed, EasySSO performs authentication. It identifies the user based on the existing session they have with their workstation.

EasySSO doesn't do authorisation - the Atlassian application is responsible for that.

1) EasySSO will liaise with your browser, and OS, then talk to your Domain Controller to identify the user - then, if successful, it will try to "feed" it to the application (Jira, Confluence, Bitbucket, Bamboo or Fisheye/Crucible).

2) It will attempt to use the username as-is (works for local and Connector AD directories) and if the user doesn't exist within the application yet, it will attempt to trigger the "first successful login" event which can (if AD integration is configured accordingly) pull the user into the application from your AD directory (works for Connector and Delegated AD directories).

3) If the application configuration allows this user to login (via Global Permissions or Application Access) - they will be logged in via SSO. Otherwise, they will be redirected to the regular login screen. (I know who you are, but I won't let you in).