I was expecting a Reset Identity which then shows the Invite option to allow testing registration. But instead, it just takes the user to an empty login page. We have a limited number of test users. Is there any way to reuse an account for end to end testing?
Hi @lsteuerTD - When you do a reset, it removes the authentication info, changes their status to ‘not invited’ as well so they will need to be re-invited before they can access again. It also removes any elevated user levels. If you re-invite, are you seeing the same behavior? One way, if you have the option, is to delete the identity and re-aggregate it so you can start from scratch.
For Reset Identity, follow this page:
Working with Identities - SailPoint Identity Services
Reset Identity is used if the user has forgotten their authentication information like their answers to knowledge-based questions.
Resetting an identity de-register the user and removes any elevated user levels they have. They must be reinvited before they regain access to Identity Security Cloud.
Reset Identity should remove the user’s registration information and return the identity to the Not Invited state. After re-inviting the user, they should be able to complete the registration flow again. If the identity is in the Not Invited state but the user is still redirected to an empty login page after re-invitation, that doesn’t appear to be the expected behavior. In that case, I’d recommend opening a SailPoint Support case so the tenant logs and authentication flow can be investigated.
Hello Lawrence,
Reset Identity is more for retesting someone’s registration and login state, not really a full “start fresh” reset. When you reset an identity, ISC de-registers the user, clears their security question answers, removes any elevated user levels, and puts the identity back to Not Invited. After that, they have to be invited again before they can get into ISC.
Reset Identity does not clear MFA. So if MFA is part of what you are testing, you will need to reset MFA separately. It will not clear on its own. Also, Reset Identity does not remove the user’s source accounts or clean up their application access. It is only resetting their ISC registration/login state.
For reusing test users, what I would normally do is reset the identity, reset MFA if that is in scope, confirm it is back to Not Invited, then invite again and re-add any elevated user levels if it was a test admin account.
If you ever need the identity completely clean, deleting it and re-aggregating is an option too, but it comes with a catch. ISC can recreate it with the same name and alias but a different internal ID, and that can affect correlation and any testing history tied to the old identity.
So for repeated end-to-end testing, I would stick with Reset Identity + Rest MFA(if any) + Reinvite as the default, and only use Delete + Reaggregate when you actually need a brand-new identity object.
One more thing I would check is the sign-in method on this identity profile. If it is set to Directory Connection / PTA, the invite flow will not look like the usual SailPoint username/password registration flow. With Directory Connection, users sign in using the password from the selected authentication source, such as AD, LDAP, Entra ID, Okta, etc.
Also make sure the selected Authentication Source is correct and that this user actually has an account on that source. If there is a mismatch there, the user will not be able to authenticate to ISC even after being invited again.
So if this identity profile is using Directory Connection, the blank login page may be tied more to the sign-in/authentication setup than to the Reset Identity action itself.