Nikolaj Posted February 21, 2020 Share Posted February 21, 2020 Hello Support, @SupportAccount I have a question regarding custom fields for users. In my case i would like to use the Attribute 5 for accountExpires. We have setup an ldap create User Import for every night. I got the right values from the import but in the wrong format. Can you help me that we are able to show the correct format in this field? And i would like to see "Account Expires" instead of "Attribute 5" for the field name. Thanks Nikolaj Thanks Nikolaj Link to comment Share on other sites More sharing options...
Nikolaj Posted March 5, 2020 Author Share Posted March 5, 2020 On 2/21/2020 at 10:32 AM, Nikolaj said: Hello Support, @SupportAccount I have a question regarding custom fields for users. In my case i would like to use the Attribute 5 for accountExpires. We have setup an ldap create User Import for every night. I got the right values from the import but in the wrong format. Can you help me that we are able to show the correct format in this field? And i would like to see "Account Expires" instead of "Attribute 5" for the field name. Thanks Nikolaj Thanks Nikolaj Hello @SupportAccount Can someone help me in this case? i would like to have a DATETIME Format for Attrib 5 or 6 Thanks Nikolaj Link to comment Share on other sites More sharing options...
Steve Giller Posted March 5, 2020 Share Posted March 5, 2020 @Nikolaj The AD attribute accountExpires is not stored as a DATETIME, the Microsoft Documentation shows that it represents the number of 100-nanosecond intervals since January 1, 1601 (UTC) I'm not sure there's any way to convert it - you might want to request this functionality as an enhancement to the Import tool. Link to comment Share on other sites More sharing options...
Steve Giller Posted March 5, 2020 Share Posted March 5, 2020 Just to follow up, converting the value to a more suitable data type has been added to the enhancements list - please keep an eye on the release notes for further updates. Link to comment Share on other sites More sharing options...
Nikolaj Posted March 6, 2020 Author Share Posted March 6, 2020 @Steve Giller Thanks for your help. You are right the attribute accountExpires is not a stored DATETIME. I saw the microsoft documentation as well. My question was if maybe Hornbill can convert it? Thanks to add it to the enhancements list. I will keep an eye on it. Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 @Steve Giller do you have any news here? thanks Nikolaj Link to comment Share on other sites More sharing options...
Steve G Posted July 2, 2020 Share Posted July 2, 2020 Hi @Nikolaj, This is now possible, if you're using v3.6.0 or above of the LDAP Import Tool. We've provided a pre-import action called LDAP Timestamp to Date & Time, which will take a field value containing an LDAP timestamp, and convert it into the YYYY-MM-DD HH:MM:SS format: So if you inject the Output of this action into one of the users fields (I've chosen Attrib 4, below) then the readable datetime will be written into the field: The user I've imported: Ansd the users record in Hornbill: Hope this helps. Steve 1 Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 Hi @Steve G great, I already saw that but was not sure if this is the right one. i will test it and let you know. Thanks Nikolaj Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 @Steve G I tried it but nothing happened. I think we are using an old import tool. here is the log entry. 2020/07/02 13:07:35 [MESSAGE] ---- XMLMC LDAP Import Utility V3.0.3 ----2020/07/02 13:07:35 How can i easily update it? thanks Nikolaj Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 @Steve G my configuration Link to comment Share on other sites More sharing options...
Steve G Posted July 2, 2020 Share Posted July 2, 2020 @Nikolaj, You'll need to grab the latest release for your OS and architecture from Github, and replace your 3.0.3 executable with that. Once that's done, you'll need to make some changes to your config. Firstly you need to remove the square brackets from the output field against the action, then hit save: Then in Attrib 5, replace the square brackets with curly braces, so it reads: {accountExpires} Or delete the value and inject it from the variable picker. Note, the newly created variables from the pre-import actions are all below the main variables. So you'll go from this: To this: Hope this helps! Cheers, Steve Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 Hi @Steve G It works like a charm. Thanks very much. best regards Nikolaj 1 Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 @Steve G one more question do you know where i can change the name Attribute 5 to expiry date? I cannot find it. thanks Nikolaj Link to comment Share on other sites More sharing options...
Nikolaj Posted July 2, 2020 Author Share Posted July 2, 2020 I found it. Best regards Nikolaj 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now