Martyn Houghton Posted January 2, 2018 Posted January 2, 2018 Is anyone else importing users 'countryCode' AD value into the Hornbill using the LDAP Importer tool? I keep getting errors when attempting to set this up. I have added the attribute to the 'LDAPAttributes' section and then attempting to map this in the 'UserMapping' section but get an error for all users. The values are the numeric ones held in AD. Is the platform expecting some other format? Cheers Martyn
TrevorKillick Posted January 3, 2018 Posted January 3, 2018 @Martyn Houghton Country Code in hornbill expects a 2 character text string the list of accepted codes can be found here:https://api.hornbill.com/_types/countryCodeType Quick google suggests you country codes are in ISO 3166-1 numeric and we are expecting ISO 3166-1 alpha-2 is ISO 3166-1 numeric a standard in AD? If so i can add a option to replace numeric with alpha 2 on country code? Kind Regards Trevor Killick
Martyn Houghton Posted January 3, 2018 Author Posted January 3, 2018 @TrevorKillick I believe ISO 3166-1 numeric is the default, but I will check and confirm. It would be good to have the option to map them anyway, as we will need this in order to make use of the country code import. Cheers Martyn
Martyn Houghton Posted January 3, 2018 Author Posted January 3, 2018 @TrevorKillick Doing a bit more digging it appears AD holds them both. https://msdn.microsoft.com/en-us/library/ms677987(v=vs.85).aspx It looks like we need to the 'c' attribute to get the alpha code rather than the LDPA attribute of the same name 'countrycode'. Cheers Martyn 1
TrevorKillick Posted January 3, 2018 Posted January 3, 2018 @Martyn Houghton Perfect ill stop looking at adding a translation function into the import now them Kind Regards Trevor Killick
Martyn Houghton Posted January 3, 2018 Author Posted January 3, 2018 @TrevorKillick Thanks. Could you update the Wiki to include a note/example using the 'c' attribute, to save other people having the issue in the future? Cheers Martyn
TrevorKillick Posted January 3, 2018 Posted January 3, 2018 @Martyn Houghton I have updated the wiki page and GitHub documentation. Kind Regards Trevor Killick
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