| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This avoids one useless search if we already have the entry_dn.
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2334
|
|
|
|
|
|
|
|
|
|
|
| |
User always receives the same error message if he changes his password
via "ipa passwd" command and the new password fails configured
password policy. He then has to investigate on his own the actual
reason why was the policy violated. This patch improves our SLAPI PWD
plugins to provide a better error message explaining the violation
reason.
https://fedorahosted.org/freeipa/ticket/2067
|
| |
|
|
|
|
|
|
| |
This removes the dependency on samba4-libs
https://fedorahosted.org/freeipa/ticket/2244
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2170
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch requires a forthcoming change in MIT libraries which allows to pass
NULL for the server_key to the krb5_pac_verify() function.
In most cases we should always only check the KDC checksum to verify the PAC
validity.
The only exception is when we are releasing a ticket to a client from another
realm. In this case the only signature we can check is the server checksum, and
we use the cross-realm key to validate in this case.
The previous code was working for normal cases because the kdc uses the same
key to create the server and the kdc checksum for a TGT, but that is not true
for evidence tickets (s4u2proxy) or cross-realm TGTs.
Fixes: https://fedorahosted.org/freeipa/ticket/2169
|
|
|
|
| |
This appeared only in the 2.1 branch and is not needed
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2038
|
| |
|
| |
|
|
|
|
|
| |
Allow to deref more than one attribute.
The attrs searched are the same for all deref attributes at this time.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: https://fedorahosted.org/freeipa/ticket/2122
|
|
|
|
| |
Fake code for now, to be rebased later
|
| |
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2037
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2036
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2036
|
|
|
|
| |
https://fedorahosted.org/freeipa/ticket/2036
|
| |
|
|
|
|
|
|
|
|
|
| |
We were not searching for objectclass so the test to se if a user had the
posixAccount attribute was failing and the user was not marked as ipa_user.
This in turn caused us to not synchronize legacy hashes by not trying to store
the userPassword attribute.
Fixes: https://fedorahosted.org/freeipa/ticket/1820
|
|
|
|
|
|
|
|
|
|
|
| |
Expiration time should be enforced as per policy only for users and only when a
password change occurs, ina ll other cases we should just let kadmin decide
whther it is going to set a password expiration time or just leave it empty.
In general service tickts have strong random passwords so they do not need a
password policy or expiration at all.
https://fedorahosted.org/freeipa/ticket/1839
|
| |
|
|
|
|
|
|
|
| |
We do the policy check so we are the only one that can calculate the new
pwd espiration time.
Fixes: https://fedorahosted.org/freeipa/ticket/1793
|
|
|
|
|
|
| |
Now that we have our own database we can properly enforce stricter constraints
on how the db can be changed. Stop shipping our own kpasswd daemon and instead
use the regular kadmin daemon.
|
|
|
|
|
|
|
| |
Although the proper values for booleans from LDAP should be only uppercase,
389ds does allow wrong cased values without complaining. And we still have some
places where the wrong case is used.
Avoid getting frustrating errors when reading these values out.
|
|
|
|
|
|
|
| |
Prevent the ipa-pwd-extop plugin from re-generating keys when kadimn is storing
a new set of keys. Only generate the userPassword and sambaXXPassword hashes.
Also avoid checking policies in this case and if history is provided avoid
regenerating the passwordHistory too.
|
|
|
|
| |
Use default policy for new principals created by kadmin
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|