[Date Prev][Date Next]
Re: (ITS#8588) microsecods in pwdFailureTime and .net Framework
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8588) microsecods in pwdFailureTime and .net Framework
- From: firstname.lastname@example.org
- Date: Tue, 14 Feb 2017 20:35:30 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Tuesday, February 14, 2017 7:37 PM +0000 email@example.com wrote:
> Full_Name: Ilya Ovchelupov
> Version: 2.4.42
> OS: Windows Server 2008R2
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (22.214.171.124)
> We are testing 2.4.42 in our environment and found an issue with
> pwdFailureTime attribute.
> It seems to me that it started after the new enhancement in 2.4.40
> (Fixed slapo-ppolicy timestamp resolution to use microseconds (ITS#7161))
> .net DirectorySearcher class doesn't support microseconds in the new
> format and we're not able to receive the attribute value.
> I'm thinking about different options how to resolve it.
> Do you know any idea how to resolve it?
The ITS system is for reporting bugs in OpenLDAP. Help requests are better
directed to the firstname.lastname@example.org list.
I would note that microsecond timestamps are per the RFC, so I would
suggest filing a bug with .NET to support the RFC.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: