On 07/03/2014 06:02 PM, Jan Cholasta wrote:
> On 3.7.2014 17:03, Petr Vobornik wrote:
>> On 2.6.2014 18:35, Petr Vobornik wrote:
>>> On 14.1.2014 15:20, Petr Viktorin wrote:
On 01/14/2014 09:33 AM, Jan Cholasta wrote:
> On 9.1.2014 16:32, Tomas Babej wrote:
>> Hi,
>>
>> For ipa
On 3.7.2014 17:03, Petr Vobornik wrote:
On 2.6.2014 18:35, Petr Vobornik wrote:
On 14.1.2014 15:20, Petr Viktorin wrote:
On 01/14/2014 09:33 AM, Jan Cholasta wrote:
On 9.1.2014 16:32, Tomas Babej wrote:
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class in
On 2.6.2014 18:35, Petr Vobornik wrote:
On 14.1.2014 15:20, Petr Viktorin wrote:
On 01/14/2014 09:33 AM, Jan Cholasta wrote:
On 9.1.2014 16:32, Tomas Babej wrote:
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class instead of Str, since these are represented
On 14.1.2014 15:20, Petr Viktorin wrote:
On 01/14/2014 09:33 AM, Jan Cholasta wrote:
On 9.1.2014 16:32, Tomas Babej wrote:
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class instead of Str, since these are represented as
LDAP Generalized Time in LDAP.
Tomas
On 01/14/2014 09:33 AM, Jan Cholasta wrote:
On 9.1.2014 16:32, Tomas Babej wrote:
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class instead of Str, since these are represented as
LDAP Generalized Time in LDAP.
Tomas
ACK.
This apparently depends on tbab
On 9.1.2014 16:32, Tomas Babej wrote:
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class instead of Str, since these are represented as
LDAP Generalized Time in LDAP.
Tomas
ACK.
--
Jan Cholasta
___
Freeipa-deve
Hi,
For ipatokennotbefore and ipatokennotafter attributes use DateTime
parameter class instead of Str, since these are represented as
LDAP Generalized Time in LDAP.
Tomas
>From cb671a7c1e746ef5f1c3de0e4ad30ae6ef42dcf1 Mon Sep 17 00:00:00 2001
From: Tomas Babej
Date: Thu, 9 Jan 2014 11:29:39 +01
