On Mon, May 09, 2016 at 08:24:13AM -0700, Sandro Santilli wrote:
Report generated by ./ldap_user_creation_report.sh 1 8 strk@kbt.io tech_dev@wildintellect.com
# LDAPv3
# base <dc=osgeo, dc=org> (default) with scope subtree
# filter: (&(createTimestamp>=20160509072412Z))
# requesting: ALL
[...]
# numResponses: 11
# numEntries: 10
I'm not sure the report is correct as the actual "createTimestamp"
is not shown for the returned records. I suspect such information
is not kept to the second resolution.
On Mon, May 09, 2016 at 05:39:30PM +0200, Sandro Santilli wrote:
On Mon, May 09, 2016 at 08:24:13AM -0700, Sandro Santilli wrote:
> Report generated by ./ldap_user_creation_report.sh 1 8 strk@kbt.io tech_dev@wildintellect.com
> # LDAPv3
> # base <dc=osgeo, dc=org> (default) with scope subtree
> # filter: (&(createTimestamp>=20160509072412Z))
> # requesting: ALL
[...]
> # numResponses: 11
> # numEntries: 10
I'm not sure the report is correct as the actual "createTimestamp"
is not shown for the returned records. I suspect such information
is not kept to the second resolution.
I found a way to extract createtimestamp:
ldapsearch -x ".." createtimestamp
Script updated. Will have it run hourly and report uid and
createtimestamp to sac, ok ?