Ticket History #8184: kadm5.acl flag restrictions don't use documented syntax

Document correct flag names for kadm5.acl

kadm5.acl entries can include restrictions which can force flag values
on or off. These flag values are parsed with krb5_string_to_flags(),
which means the flag names are the ones for default_principal_flags,
not the ones for kadmin addprinc/modprinc.

(cherry picked from commit ef21069070c1eb2ab1ade1d1406f5cd3920c83a9)
(cherry picked from commit 185114aa35508e46c90354d8ddea76f65fe556d8)

https://github.com/krb5/krb5/commit/07105895985e4c55a7bbf2bfc8fd23d5b8c95b95
Author: Greg Hudson <ghudson@mit.edu>
Committer: Tom Yu <tlyu@mit.edu>
Commit: 07105895985e4c55a7bbf2bfc8fd23d5b8c95b95
Branch: krb5-1.12
doc/admin/conf_files/kadm5_acl.rst | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)

Log invalid restrictions strings

In kadm5int_acl_parse_restrictions(), output a log message if we break
out of the parsing loop with an error. The current structure of the
loop makes it difficult to pinpoint the bad restrictions field, so
just output the whole string.

(cherry picked from commit e9eaafeab12b2b62595f4dff2fca3345b2d95b4a)
(cherry picked from commit 1ff2ecc7890ae4b843c77c2ba68f5a152806bf05)

https://github.com/krb5/krb5/commit/16757adc05ecc9605f306b7b0c3147ae09133cd3
Author: Greg Hudson <ghudson@mit.edu>
Committer: Tom Yu <tlyu@mit.edu>
Commit: 16757adc05ecc9605f306b7b0c3147ae09133cd3
Branch: krb5-1.12
src/lib/kadm5/srv/server_acl.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)