Password sync issue for users with different username and samaccountname

[chetan_falke]

We are facing problem for users who are having different samaccountname and username. When these users are trying to change the password from AD or Okta their password is not getting sync back.

We have observed this is because of correlation field which is set as username in password filter Json which is present in password sync agent in AD.  

Our concern is can we use AD attribute like employee id or extension attribute 15 for password sync agent instead of samAccount Name.

Please find the below json :

{
  "saviynt": {
    "baseUrl": "hostname",
    "userName": "admin",
    "password": "XXXXXX",
    "notificationUrl": "hostname",
    "getUserUrl": "hostname",
    "correlation": "employeeid",
    "endpoints": "abc,def",
    "sourceEndpoint": "def"
},
  "filter": {
    "enabled": false,
    "policy": {
      "enforce":  "local",
      "local": {
        "minChars": 10,
        "maxChars": 20,
        "lowerCases": 1,
        "upperCases": 1,
        "numbers": 1,
        "specials": 1
      }
    }
  },
  "notification": {
    "enabled": true
  }
}

[rushikeshvartak · Accepted solution]

It should be user attribute 

[chetan_falke]

If it should be user attribute, then can we use custom properties of users too and how to do mapping of user attribute with AD attribute in Password agent?

[rushikeshvartak · Accepted solution]

    "correlation": "customproperty1",

[chetan_falke]

Where do we define AD attribute to be mapped?

For Eg. i have to mapp extensionattribute12 with customproperty1

[rushikeshvartak]

That will be mapped in ad connection isn’t it