Re: [Freeipa-users] Getting Samba to authenticate against FreeIPA

2013-03-25 Thread Marc Grimme
Am 24.03.2013 18:14, schrieb Martin: That guide at techslaves.org sounds like a perfect match for our needs, unfortunately the map and reality didn't quite match... Point 4.3 says: 4.3. Test the CLI. With an “admin” (or equivalent priv) kerberos ticket, try creating a new group:

Re: [Freeipa-users] Account Expiration

2013-03-25 Thread Petr Vobornik
On 03/24/2013 05:50 PM, Dmitri Pal wrote: On 03/23/2013 03:58 AM, James James wrote: Hi Petr Can you (or somebody else ) give me some hints to use a calendar widget in the UI ? In the past we said that there is no calendar widget mature enough to meet our requirements. Has this changed? Is

Re: [Freeipa-users] bind-dyndb-ldap howto use wildcard

2013-03-25 Thread Petr Spacek
On 23.3.2013 18:17, Marc Roos wrote: I dont seem to get the wildcard working. Is this a correct way of creating a dns record DN: idnsName=*.241.36.65,idnsName=rbl.test.com,dc=office,dc=local objectClass: idnsRecord aRecord: 127.0.0.1 idnsName: *.241.36.65 If I do a dig on the nameserver on

Re: [Freeipa-users] Account Expiration

2013-03-25 Thread Dmitri Pal
On 03/25/2013 08:27 AM, Simo Sorce wrote: On Mon, 2013-03-25 at 10:42 +0100, Petr Vobornik wrote: On 03/24/2013 05:50 PM, Dmitri Pal wrote: On 03/23/2013 03:58 AM, James James wrote: Hi Petr Can you (or somebody else ) give me some hints to use a calendar widget in the UI ? In the past we

[Freeipa-users] User admins for different groups

2013-03-25 Thread Philipp Richter
Hi, I am trying to do the following: We have some branch offices at different locations. We want to use one ipa-server with replicas in each branch office. Each branch office should have it's own set of administrators who should be able to create/modify/delete users for its own branch but

Re: [Freeipa-users] error setting up replication client

2013-03-25 Thread Ade Lee
Ok. The log directory being empty is indicative of the server not having started - which is what I suspected based on the output you provided. There might have been some indication in /var/log/messages or in /var/log/audit/audit.log (for selinux) as to why this happened. If this does happen