Skip to content
Snippets Groups Projects
Commit deab2937 authored by Howard Chu's avatar Howard Chu
Browse files

Disclaimer for behavior in a master/slave replication environment

parent 75eecdc5
No related branches found
No related tags found
No related merge requests found
...@@ -491,7 +491,7 @@ policy proposal. ...@@ -491,7 +491,7 @@ policy proposal.
.SH OPERATIONAL ATTRIBUTES .SH OPERATIONAL ATTRIBUTES
.P .P
The operational attributes used by the The operational attributes used by the
.B passwd_policy .B ppolicy
module are stored in the user's entry. Most of these attributes module are stored in the user's entry. Most of these attributes
are not intended to be changed directly by users; they are there are not intended to be changed directly by users; they are there
to track user activity. They have been detailed here so that to track user activity. They have been detailed here so that
...@@ -500,6 +500,19 @@ the ...@@ -500,6 +500,19 @@ the
.B ppolicy .B ppolicy
module. module.
.P
Note that the current IETF Password Policy proposal does not define
how these operational attributes are expected to behave in a
replication environment. In general, authentication attempts on
a slave server only affect the copy of the operational attributes
on that slave and will not affect any attributes for
a user's entry on the master server. Operational attribute changes
resulting from authentication attempts on a master server
will usually replicate to the slaves (and also overwrite
any changes that originated on the slave).
These behaviors are not guaranteed and are subject to change
when a formal specification emerges.
.B userPassword .B userPassword
.P .P
The The
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment