Terminology improvements: use allow list

See: https://tools.ietf.org/id/draft-knodel-terminology-01.html
Signed-off-by: Christian Heimes <cheimes@redhat.com>
Reviewed-By: Alexander Bokovoy <abbra@users.noreply.github.com>
Reviewed-By: Rob Crittenden <rcritten@redhat.com>
This commit is contained in:
Christian Heimes 2020-06-11 14:28:31 +02:00 committed by Florence Blanc-Renaud
parent 5c09dcdb98
commit 3ce816ba77
3 changed files with 3 additions and 3 deletions

View File

@ -27,7 +27,7 @@ these two are assigned the same indicator to represent a brute-force hardened fo
By requiring certain authentication indicators to a user, we can force a user to be authenticated with one of
the mechanisms associated with those auth indicators to obtain a ticket.
By defining a white list of authentication indicators to a service, we can allow a user to use the service
By defining an allow list of authentication indicators to a service, we can allow a user to use the service
only if the user obtained a ticket with at least one of those indicators included.
### Note

View File

@ -584,7 +584,7 @@ class host(LDAPObject):
'krbprincipalauthind*',
cli_name='auth_ind',
label=_('Authentication Indicators'),
doc=_("Defines a whitelist for Authentication Indicators."
doc=_("Defines an allow list for Authentication Indicators."
" Use 'otp' to allow OTP-based 2FA authentications."
" Use 'radius' to allow RADIUS-based 2FA authentications."
" Use 'pkinit' to allow PKINIT-based 2FA authentications."

View File

@ -541,7 +541,7 @@ class service(LDAPObject):
'krbprincipalauthind*',
cli_name='auth_ind',
label=_('Authentication Indicators'),
doc=_("Defines a whitelist for Authentication Indicators."
doc=_("Defines an allow list for Authentication Indicators."
" Use 'otp' to allow OTP-based 2FA authentications."
" Use 'radius' to allow RADIUS-based 2FA authentications."
" Use 'pkinit' to allow PKINIT-based 2FA authentications."