User17055991943374153411 (Customer) asked a question.
Hi all,
Currently we manage proxyAddresses in AD directly, but I would like to add the option to add new proxyAddresses via Okta. I have added the field from AD and set up an Array field in Okta (mastered by Okta) and I can add new proxyAddresses no problem. However, if there are existing proxyAddresses in AD, these will be overwritten by Okta as soon as a new one is added in Okta. This is a problem as in theory, someone could still manually add a proxyAddress in AD if they wanted, but then the next time someone adds one via Okta it'd be erased without anyone noticing (until the user notices they've stopped receiving mail). Is it possible to have Okta add new proxyAddresses without overwriting existing ones? Thanks!
Hi, @User17055991943374153411 (Customer)
Thank you for posting on our Community page!
Here is a previously answered question on the topic,
https://support.okta.com/help/s/question/0D54z00006sT4LECA0/will-an-ad-import-overwrite-existing-users?language=en_US
And an interesting article
https://devblogs.microsoft.com/scripting/how-can-i-add-an-email-address-to-the-proxyaddresses-attribute/
Thank you for reaching out to our Community and have a great day!
--
Join the discussion for the Ask Me Anything online event on May 23, 2024 with Okta Tactical Edge Product Experts
Hi Laura,
The first link does not answer the question I have, which is specific to overwriting the proxyAddress field, not importing users from AD generally.
The second link explains how to do it with PowerShell without overwriting existing proxyAddresses, which I am aware how to do, but does not explain how to do it with Okta, which is what I am asking.
I did find a workaround, but it's cumbersome and I would be interested in a better option.
This allows adding a proxyAddress to either the proxyAddresses attribute in Okta, or directly to the proxyAddresses attribute in AD, and both a) having the data in Okta and b) not inadvertently overwriting the data in AD. If someone goes to add a proxyAddress via Okta, all the existing proxyAddresses are already filled out in the array, so they'd have to consciously delete one to remove it. And if they did, that change would be reflected in both Okta and AD as expected. It works, it's just a bit clunky due to having two proxyAddress-related fields in Okta, only one of which is writeable within Okta, and needing a Workflow to keep one of them up to date.