Hi Colin,
the issue with "Z" is that it is interpreted by LAM as time wildcard and
not kept as character. I will check how this can be avoided properly.
Exactly, the proposal would be to use a string/text field. Text fields
in LAM custom fields also support a date picker (only date, not time).
If this is a new attribute and not used yet I suggest to use a simple
text attribute. This way you are not bound to the AD specific date
format and can use something simple as Y-m-d which is also supported by
LAM's text field right now.
Best regards
Roland
Am 25.06.23 um 11:14 schrieb [email protected]:
Hi Roland,
thanks for your quick response.
Do I get you right that you're suggesting to create a new AD attribute with
some string type instead of generalized time?
And then use custom field of type LDAP date in LAM? Or where you more thinking
of also using a text field in LAM with regex? The latter would have the
downside of not offering a date picker...
And what issues with the "Z" are you referring to? Is the difference between "Z" only in
LAM vs ".0Z" in AD even still a problem if I use a AD text attribute instead of generalized time?
Thanks and regards,
Colin
-----Ursprüngliche Nachricht-----
Von: Roland Gruber <[email protected]>
Gesendet: Samstag, 24. Juni 2023 20:20
An: [email protected]
Betreff: Re: [Lam-public] Custom Field Type LDAP Date not mapping correctly to
Windows Active Directory Generalized Time field
Hi Colin,
I think this is because AD uses a different date format.
LAM expects "19940413000000Z" while you need "19940413000000.0Z".
The solution would be to use a text field with date type validation. But looks like the
"Z" is causing issues. Will dig deeper and provide feedback the next few days.
Best regards
Roland
Am 24.06.23 um 13:22 schrieb [email protected]:
Hello Roland,
We recently set up LAM Pro with Active Directory for managing our
theatre internal user accounts.
In general it works fine, now I’m about to add some custom attributes
to AD and map them in LAM accordingly.
Where I’m having trouble is with “LDAP date” type custom fields.
I added a “birthday” attribute in AD with Type “Generalized Time”.
When I enter a date in AD directly I can also see it in the format
“19940413000000.0Z” in LAM – but it doesn’t seem to map it to a date
in the configured d.m.Y format.
And vice versa – if I enter a date through the date picker and click
save – it also throughs an error saying:
“LDAP-Fehler, der Server meldet: Invalid syntax - 00000057: LdapErr:
DSID-0C091050, comment: Error in attribute conversion operation, data
0, v4f7c“
How can I resolve this? Am I missing any additional settings that are
needed to make the mapping work?
Best regards,
Colin
Colin Weitmann
IT Koordination
E
T
W
<mailto:[email protected]> [email protected]
0177 / 4959296
<http://www.tudk.de/> www.tudk.de
Theater unter den Kuppeln e.V.
Gräbleswiesenweg 32
70771 Leinfelden-Echterdingen
<http://www.tudk.de/> www.tudk.de
Volksbank Filder
IBAN: DE69 6116 1696 0260 0580 09
BIC: GENODES1NHB
USt-ID: DE147806147
Vertretungsberechtigter Vorstand:
Ralph Brückner, Matthias Tränkle, Barbara Thome
Amtsgericht Stuttgart | VR 220295
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public
