Petr Viktorin 4f89decc9a ldap2.has_upg: Raise an error if the UPG definition is not found ... The UPG Definition is always present in IPA; if it can not be read it's usually caused by insufficient privileges. Previously the code assumed the absence of the entry meant that UPG is disabled. With granular read permissions, this would mean that users that can add users but can't read UPG Definition would add users without UPG, and the reason for that would not be very clear. It is better to fail early if the definition can't be read. Raise an error if the UPG Definition is not available. This makes read access to it a prerequisite for adding users. Part of the work for: https://fedorahosted.org/freeipa/ticket/3566 Reviewed-By: Martin Kosek <mkosek@redhat.com>		2014-05-29 16:22:37 +02:00
..
__init__.py	Change FreeIPA license to GPLv3+	2010-12-20 17:19:53 -05:00
dogtag.py	Convert remaining backend code to LDAPEntry API.	2013-12-16 14:44:19 +01:00
join.py	Add logging to join command	2013-03-25 10:58:23 +01:00
ldap2.py	ldap2.has_upg: Raise an error if the UPG definition is not found	2014-05-29 16:22:37 +02:00
rabase.py	Drop --selfsign server functionality	2013-04-15 16:56:12 -04:00
xmlserver.py	Store session cookie in ccache for cli users	2012-06-14 14:02:26 +02:00