Error Ldap sync

FAIL: Couldn't search with this input due to java.naming.provider.url property does not contain a URL
FAIL: java.naming.provider.url property does not contain a URL


Security tab for the tenant has the LDAP url and credentials

sync_directory_with_ldap.sh has all the tenant urls and admin credentials to pull users and groups from Ldap

3replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Sorry for the confusion.  The configuration defined for LDAP authentication is different from the configuration used in directory sync.  We can use directory sync to get the user, user group membership from directory service but still use Incorta native authentication or SSO. 

    Please specify the LDAP server access in the property file.

      • Srinivasan
      • Confi Com
      • Srinivasan
      • 7 mths ago
      • Reported - view

      Dylan Wan 


      Thank you. I noticed that the ldap.configuration property file was placed at a different location. Got that fixed. Now I was able to get users and Groups added thru ldap sync. However, user is not able to login.  Shows invalid user name and password. Partner is using LDAP password only. Can you please help.?

      ERROR: [14:00:13] [POST/authservice/login] {
      ERROR: [14:00:13] [POST/authservice/login]  "result": 15,
      ERROR: [14:00:13] [POST/authservice/login]  "error": "INC_02020000: Invalid username or password.",
      ERROR: [14:00:13] [POST/authservice/login]  "message": "INC_02020000: Invalid username or password."
      ERROR: [14:00:13] [POST/authservice/login]} [com.incorta.webapi.AbstractServlet.writeError]

    • Srinivasan Can you check if the loginname is mapped to the same attribute?  Also, what is the UserType? If the intention is to use LDAP login, the user type need to be set to LDAP, not Internal in the ldap.configuration property  file.

Like Follow
  • 7 mths agoLast active
  • 3Replies
  • 19Views
  • 2 Following

Product Announcement

Incorta 5 is now Generally Available