Hi,we have investigated the following issue. The account naming attributes (cn, dn, name) for service accounts are not updated on update. The assumption was, that this is handled via the ACCOUNTNAMERULE, but seems like it is not the case for service ...
Hi, as it is currently not supported to set the account name for service accounts to read only, we need to find a workaround to enforce our naming convention. Therefore we thought about two options:1. Regex to check account name => not possible as th...
Hi @dgandhi ,really appreciate the elaborated answer! We will try to use the your example and adapt it to our current implementation and requirements.One last question. The provided script is added to the UPDATEACCOUNTJSON right?Thanks!
Hi @dgandhi, if that is possible, yes. My assumption based on the statement is, that we first need to import the AD accounts and afterwards need to import via sav4sav (which I'm still not 100% sure, if this can be achieved by sav4sav)
@rushikeshvartak thanks for the response. Can you please elaborate a little bit on that, how this is possible for the AD account objects in Saviynt. So you telling, that we can update the values on the AD account object via sav4sav?
@Enakshi we are facing the same issue for personal accounts. In our case primary and admin. The mentioned field is not set on the request form, but we have dedicated endpoints for every account type:Endpoint1: AD PrimaryEndpoint2: AD AdminWe also hav...
