Merge pull request circleci#1921 from circleci/update-caution-to-note-in-auth-doc

michelle-luna · web-flow · commit c0d33742c9de · 2018-01-16T15:07:39.000-08:00
change caution to note and rework per Anton
diff --git a/jekyll/_cci2/authentication.md b/jekyll/_cci2/authentication.md
@@ -37,4 +37,4 @@ This section provides the steps to configure LDAP in the management console (Rep
 
 A user who logs in will be redirected to the Accounts page of the CircleCI application with a Connect button that they must use to connect their GitHub account. After they click Connect, an LDAP section with their user information (for example, their email) on the page will appear and they will be directed to authenticate their GitHub account. After authenticating their GitHub account users are directed to the Builds page to use CircleCI.
 
-**Caution:** After a user has authenticated with LDAP and connected their GitHub account, disabling or removing a user from LDAP/AD will not log them out. A user who is removed from LDAP/AD will be able to access CircleCI as long as that user stays logged in (because of cookies). As soon as the user logs out or the cookie expires, they will not be able to log back in. A better handling for this case will be implemented as an update to this feature preview.
+**Note:** A user who has authenticated with LDAP and is then removed from LDAP/AD will be able to access CircleCI as long as they stay logged in (because of cookies). As soon as the user logs out or the cookie expires, they will not be able to log back in. A users' ability to see projects or to run builds is defined by their GitHub permissions. Therefore, if GitHub permissions are synced with LDAP/AD permissions, a removed LDAP/AD user will automatically lose authorization to view or access CircleCI as well.

Original file line number	Diff line number	Diff line change
`@@ -37,4 +37,4 @@ This section provides the steps to configure LDAP in the management console (Rep`
`37`	`37`
`38`	`38`	`A user who logs in will be redirected to the Accounts page of the CircleCI application with a Connect button that they must use to connect their GitHub account. After they click Connect, an LDAP section with their user information (for example, their email) on the page will appear and they will be directed to authenticate their GitHub account. After authenticating their GitHub account users are directed to the Builds page to use CircleCI.`
`39`	`39`
`40`		`-Caution: After a user has authenticated with LDAP and connected their GitHub account, disabling or removing a user from LDAP/AD will not log them out. A user who is removed from LDAP/AD will be able to access CircleCI as long as that user stays logged in (because of cookies). As soon as the user logs out or the cookie expires, they will not be able to log back in. A better handling for this case will be implemented as an update to this feature preview.`
	`40`	+Note: A user who has authenticated with LDAP and is then removed from LDAP/AD will be able to access CircleCI as long as they stay logged in (because of cookies). As soon as the user logs out or the cookie expires, they will not be able to log back in. A users' ability to see projects or to run builds is defined by their GitHub permissions. Therefore, if GitHub permissions are synced with LDAP/AD permissions, a removed LDAP/AD user will automatically lose authorization to view or access CircleCI as well.