Steve Giller Posted May 31, 2018 Share Posted May 31, 2018 First attempt at setting up the new import, so it's probably a stupid mistake on my part. I'm getting the error:Config Error - No LDAP Credentials Missing KeySafe Id As you can imagine, I have created and set a KeySafe Id (and if I hadn't, that error is very clear!) but I've clearly not done it correctly. The first question is - would my error be in the import config, or in the KeySafe Id itself? Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Can you post a screen grab of the LDAP Server Tab from the Import Configuration please. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 Sorry - forgot to do that first time. Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Can you confirm the command line you are using (with the API Key removed) please. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 LDAP_User_Import.exe -config=dev-ldap-import -logprefix=test_3_ -dryrun=true -instanceid=derbycollege -apikey= Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Thanks, and the id dev-ldap-import is exactly as it displays in the URL of the configuration? Can you also post the log file content again removing any API Key. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 Yes - I even re-ran the command after copy-pasting dev-ldap-import from the url just to be safe. 2018/05/31 11:17:35 [MESSAGE] ---- XMLMC LDAP Import Utility V3.0.3 ---- 2018/05/31 11:17:35 [MESSAGE] Flag - config dev-ldap-import 2018/05/31 11:17:35 [MESSAGE] Flag - logprefix test_3_ 2018/05/31 11:17:35 [MESSAGE] Flag - dryrun true 2018/05/31 11:17:35 [MESSAGE] Flag - instanceid derbycollege 2018/05/31 11:17:35 [MESSAGE] Flag - apikey 2018/05/31 11:17:35 [MESSAGE] Flag - apitimeout 60 2018/05/31 11:17:35 [MESSAGE] Flag - workers 1 2018/05/31 11:17:35 [MESSAGE] Loading Configuration Data: dev-ldap-import 2018/05/31 11:17:36 [ERROR] Config Error - No LDAP Credentials Missing KeySafe Id Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Thank for that, can you copy and paste the JSON output from the Debug tab and ping it over in a PM please. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF So everything looks configured correctly except on your Instance i can see lots of errors data:entityGetRecord() Method call results: failure Its possible the account associated to the API key doesn't have rights to load the configuration and this is not correctly reflected in the Import Errors, does the associated account have the role 'User Import' ? Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 Aha! No - I missed that one. Is that new to version 3? The same key works fine for the existing imports but they're on 2.4.1 Update - I added that role and still getting the same error - is there a delay in applying the change or should it be instant? Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF So the Role has bene there for a while and we keep it up to date with any additional rights needed to run the imports, i cannot replicate this at all are you ok to share your API Key? This will let me see what your import is doing in the background without doing the import. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 Sent you a DM Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Thanks ok so on the instance the KeySafeId is saved as 0, in the Import Configuration can you set the Authentication to "None" save then refresh and set it back to the LDAP Authentication you created and save again? Its very odd for this to happen as the correct id shows in debug but not in the database. Kind Regards Trevor Killick Link to comment Share on other sites More sharing options...
Steve Giller Posted May 31, 2018 Author Share Posted May 31, 2018 That's fixed it - I can only assume that there was an issue saving for some reason. Thanks for the help @TrevorKillick Link to comment Share on other sites More sharing options...
TrevorKillick Posted May 31, 2018 Share Posted May 31, 2018 @DeadMeatGF Great, glad thats working now. Will take a look and see if there is anything i can do to prevent this type of issue from occurring again. Kind Regards Trevor Killick 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