On 02/18/2016 01:00 PM, Mark Reynolds wrote:
>
>
> On 02/18/2016 03:55 PM, Mark Reynolds wrote:
>>
>>
>> On 02/18/2016 03:43 PM, jfillman(a)central1.com wrote:
>>> I'm migrating a DS from RHDS 8.2 to 389 DS and i'm having an issue
>>> attributes of type 'Generalized Time'.
>>>
>>> One my old LDAP server, i could set dates in this format:
>>> 20160215133951.842
>>>
>>> 389 DS 1.2.11 doesn't seem to allow this local time version. Is
>>> there any way to enable/allow this?
>> Not that I know of, but "20160215133951.842" does not seem to
>> comply with the LDAP RFC for generalized time:
>>
>>
https://tools.ietf.org/html/rfc4517#section-3.3.13
> Actually it does allow for the period, so it should be valid...
> Please open a ticket to have this investigated:
>
>
https://fedorahosted.org/389/newticket
Not sure I'm reading this correctly, but according to this notation,
g-time-zone needs to be there after fraction which contains dot or
comma and is optional.
GeneralizedTime = century year month day hour
[ minute [ second / leap-second ] ]
[ fraction ]
g-time-zone
And g-time-zone has to end with Z or g-differential.
g-time-zone = %x5A ; "Z"
/ g-differential
g-differential = ( MINUS / PLUS ) hour [ minute ]
So, it looks to me the allowed formats are ...
Examples:
199412161032Z
199412160532-0500
199412160532+0500
as well as
20141006133000.0Z
20141006133000.0-0500
20141006133000.0+0500
Could it be possible to try adding 'Z' at the end of
20160215133951.842 and see how 389-ds-base-1.2.11.x reacts?