Sailpoint IdentityNow – Lifecycle State Does Not Match Technical Name Case
In Sailpoint IdentityNow lifecycle states describe a user’s status in a company. Once you define and start importing from an authoritative source, you might get the following message for your identity – Lifecycle State Does Not Match Technical Name Case –
This status occurs when the value from the source system matches the technical name of the lifecycle state, but the source system value’s name uses one or more uppercase letters.
The technical name is always lower case.
The above user was imported with an Employee Status = Active, which was the initial cause for the lifecycle issue.
After adding the Employee Status = active and importing the employee source again. Now you should be able to see the correct lifecycle state for the employee.
That active lifecycle should initiate any provisioning configuration attached in your system.
Please keep visiting us for more Sailpoint IdentityNow notes.
Gabriel Magarino
Gabriel Magarino – Senior Security Manager | IAM Evangelist - Experienced leader with over 20 years in the IT and cybersecurity industry, specializing in Identity & Access Management. Expert in Okta, One Identity, SailPoint (IdentityIQ & IdentityNow), OneLogin, Delinea, and CyberArk. Passionate about exploring IAM and emerging technologies, coaching, and training IAM teams. Holds a Master’s in Computer Science and multiple certifications, including Okta Professional & Administration, One Identity Architect & Instructor, SailPoint Identity Now, ITIL, Scrum Master, among others. Currently pursuing a PhD with a focus on Computer Science and Artificial Intelligence.