summaryrefslogtreecommitdiffstats
path: root/ipalib/plugins/virtual.py
Commit message (Collapse)AuthorAgeFilesLines
* Add default success/failure output logging.Rob Crittenden2011-02-141-1/+1
| | | | | | | | | | Request logging on the server only happened if you added verbose=True or debug=True to the IPA config file. We should log the basics at least: who, what, result. Move a lot of entries from info to debug logging as well. Related to ticket 873
* Move Virtual Operations container under cn=etcSimo Sorce2011-01-141-1/+1
| | | | Fixes: https://fedorahosted.org/freeipa/ticket/759
* Change FreeIPA license to GPLv3+Jakub Hrozek2010-12-201-5/+5
| | | | | | | | | | The changes include: * Change license blobs in source files to mention GPLv3+ not GPLv2 only * Add GPLv3+ license text * Package COPYING not LICENSE as the license blobs (even the old ones) mention COPYING specifically, it is also more common, I think https://fedorahosted.org/freeipa/ticket/239
* First pass at enforcing certificates be requested from same hostRob Crittenden2009-10-211-22/+15
| | | | | | | | | | | | We want to only allow a machine to request a certificate for itself, not for other machines. I've added a new taksgroup which will allow this. The requesting IP is resolved and compared to the subject of the CSR to determine if they are the same host. The same is done with the service principal. Subject alt names are not queried yet. This does not yet grant machines actual permission to request certificates yet, that is still limited to the taskgroup request_certs.
* Raise more specific error when an Objectclass Violation occurs Fix the ↵Rob Crittenden2009-09-141-3/+3
| | | | virtual plugin to work with the new backend
* Implement support for non-LDAP-based actions that use the LDAP ACI subsystem.Rob Crittenden2009-07-101-0/+73
There are some operations, like those for the certificate system, that don't need to write to the directory server. So instead we have an entry that we test against to determine whether the operation is allowed or not. This is done by attempting a write on the entry. If it would succeed then permission is granted. If not then denied. The write we attempt is actually invalid so the write itself will fail but the attempt will fail first if access is not permitted, so we can distinguish between the two without polluting the entry.