When multiple profile sources are used in Okta without attribute level sourcing enabled, is Okta attributes' precedence correct?

In Okta, when multiple profile sources are used without attribute level sourcing enabled, the attributes sourced from different sources do not follow a predictable precedence due to the lack of defined rules for how these sources should interact. This means that attributes may not be sourced consistently, as Okta will take the value from a source but won’t necessarily have a clear hierarchy to determine which source's value to prefer.

When attribute level sourcing is not enabled, the system does not apply a structured mechanism to resolve potential conflicts between attributes pulled from various sources. This can lead to unexpected results where the attributes may not always reflect the desired values from the preferred source, thus confirming the response that the attributes' precedence is not correct in this scenario.

When attribute level sourcing is enabled, Okta can prioritize attributes based on the specific rules defined for each attribute, allowing for more controlled and predictable behavior regarding which profile source's attributes are ultimately used. However, in the absence of that, there is no guarantee on precedence, making it essential to enable this feature when dealing with multiple sources.