IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-24 16:10:02 -06:00
Code Issues Packages Projects Releases Wiki Activity
ac68ea3c6c
freeipa/install
History
Rob Crittenden ac68ea3c6c Add default roles and permissions for HBAC, SUDO and pw policy 
Created some default roles as examples. In doing so I realized that
we were completely missing default rules for HBAC, SUDO and password
policy so I added those as well.

I ran into a problem when the updater has a default record and an add
at the same time, it should handle it better now.

ticket 585
2011-02-22 10:02:24 -05:00
..
conf rename static to ui 2011-01-20 14:12:47 +00:00
html error handling style 2011-01-25 16:47:09 -05:00
migration Fix migration page 2011-02-11 13:28:22 -05:00
po Update Polish & Ukrainian translations 2011-02-18 10:30:32 -05:00
share Add default roles and permissions for HBAC, SUDO and pw policy 2011-02-22 10:02:24 -05:00
tools Fixed in ipa-server-install help and man page 2011-02-18 10:00:48 -05:00
ui search filter focus afdter a search loads, focus moved to the search filter text box, tyhe most likely thing that the user will want to change on the page. 2011-02-21 18:32:29 -05:00
updates Add default roles and permissions for HBAC, SUDO and pw policy 2011-02-22 10:02:24 -05:00
configure.ac rename static to ui 2011-01-20 14:12:47 +00:00
Makefile.am rename static to ui 2011-01-20 14:12:47 +00:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

README.schema 

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.