We currently have attribute sync working fine and we realize the a difference in the case for an identity attribute vs account attribute would be treated as a difference and therefore attribute sync even would trigger. However, this is undesirable for us and therefore trying to find a solution for this. Any thoughts on the below?
Is there any attribute config via the API or at the source level that can help make it case insensitive? like correlation config can be made case insensitive.
Is there a way to convert the value to a lower or upper case when reading data from the source so it matches the case of an identity attribute?
Thank you for your response. May be this is the info I should’ve added in my initial post but anyways,
Our auth source provides us the value consistently in lower case, so applying transform here will not add any value.
Our target system has 90% matching the lower case from #1 but the remaining values in target are in Title case or Upper case. Unfortunately, even though it’s only 10%, we are talking about 10k users.
Hopefully that explains the complexity of our situation.
Just spoke with the PM for attribute sync. We expect that the 8am attribute sync should evaluate all accounts and set non-matching ones to the case the identity uses (i.e. the 10% non-matching accounts will be updated with the lowercase that identity attribute uses). In other words, this should be a temporary problem for you unless there’s a factor of which we’re unaware. Our Product Manager for attribute sync would be glad to have a 30 minute chat with you to assess the issue. You could schedule with him here: