If a Security Profile is created as user@DOMAIN, will it match an AutoSys job owner defined as user@domain?
During the validation process within the AutoSys code, the security profile name is internally converted to uppercase. Therefore, the specific casing used in the job definition's owner field does not need to match the casing used when the profile was created in autosys_secure.
AutoSys prevents the creation of duplicate security profiles that differ only by case.
For example, if [email protected] already exists as a Security Profile, the system will not allow the creation of [email protected]