Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Unable to clear/remove proxyAddresses in AD via UPDATEACCOUNTJSON

alex1
New Contributor III
New Contributor III
Hi,

We have an issue to remove or clear the proxyAddresses attribute in AD from Saviynt. This is what we are trying to do:


Removal:
 
Have a user in AD with the following proxyAddresses as multi valued attributes:
X500License
smtp:UAT-User@domain.mail.onmicrosoft.com
smtp:UAT-User@domain.onmicrosoft.com
SIP:UAT.UPN@domain.com
SMTP:UAT.UPN@domain.com
 
Try to send an empty array (with or without SUPPORTEMPTYSTRING set to True/False)
 
Update goes through, but no changes in AD.
 
For changing specific proxyAddresses:
Have a user in AD with the following proxyAddresses as multi valued attributes:
X500License
smtp:UAT-User@domain.mail.onmicrosoft.com
smtp:UAT-User@domain.onmicrosoft.com
SIP:UAT.UPN@domain.com
SMTP:UAT.UPN@domain.com
SMTP:UAT.WRONG.UPN@domain.com
 
Map proxyAddresses attribute to user attribute as: X500License,smtp:UAT-User@domain.mail.onmicrosoft.com,smtp:UAT-User@domain.onmicrosoft.com,SIP:UAT.UPN@domain.com,SMTP:UAT.UPN@domain.com
 
(Where the wrong SMTP is removed)
 
Task is completed, no changes in AD is made. 
 
Adding additional proxyAddresses and replacement of Primary is fine, just removal that doesnt work.

But, we have tried to hardcode values as:

"proxyAddresses":[],
"proxyAddresses":'',
"proxyAddresses":\"\",
and so on. I have also tried to hardcode the changed value:
customproperty62 = X500License,smtp:UAT-User@domain.mail.onmicrosoft.com,smtp:UAT-User@domain.onmicrosoft.com,SIP:UAT.UPN@domain.com,SMTP:UAT.UPN@domain.com 
proxyAddresses: ${user.customproperty62.replace(',','\",\"')}
But basically, no change is made.

All additions and creation are working, it just removal that doesn't work no matter if we hardcode it or use our logic. 

I have added idea here as well, https://ideas.saviynt.com/ideas/EIC-I-5689

[This message has been edited by moderator to merge reply comment]
 
7 REPLIES 7

vivek9237
Regular Contributor
Regular Contributor

@alex1 Can you try with this config - 

{
  "proxyAddresses": {
    "REPLACE": []
  }
}
Regards,

Vivek Mohanty


If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

alex1
New Contributor III
New Contributor III

Hi,

Thanks for your suggestion. Unfortunately it didn't do anything from what I could see, we still see the same behavior as described in the ticket. Even if we are able to send an empty array, it doesn't update anything and just stays as is.

vivek9237
Regular Contributor
Regular Contributor

Try with this once-

 

{
  "proxyAddresses": {
    "REPLACE": [""]
  }
}

Also, try with SUPPORTEMPTYSTRING as TRUE

 

Regards,

Vivek Mohanty


If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

alex1
New Contributor III
New Contributor III

I have tried both ways, with and without SUPPORTEMPTYSTRING set to true and false. In the logs it looks correct and it sends an empty array, but when you look at the result in AD nothing is changed.

alex1
New Contributor III
New Contributor III

Hi again, 

I tried hard coding some values (using SUPPORTEMPTYSTRING to false) I got this to work, now I just have to figure out how to include it when we are using our attributes, but this is a step in the right direction! Thank you for your help and tips!

But the basic version of 

{
  "proxyAddresses": {
    "REPLACE": []
  }
}

Works for clearing,

and doing:

{
  "proxyAddresses": {
    "REPLACE": ["smtp:upn@domain.com"]
  }
}

 

Replaces everything that is currently in the field!

vivek9237
Regular Contributor
Regular Contributor

What is the modification list that is getting logged in WSRETRY logs?
The log should start with a text - "MOdification List-".

Regards,

Vivek Mohanty


If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

alex1
New Contributor III
New Contributor III

alex1_0-1712930371038.png

This is what I found the logs