I'd test in an InPrivate browsing window to ensure you don't have unexpired cookies with the previous user information. If that works then you know you need to delete cookies. WebSphere creates a JSESSIONID cookie always and for LDAP/SAML authentication it adds a LTPA token cookie as well. Out of box a LTPA token is valid for 2 hours but many organizations extend this as it causes users to get logged out even if they're active if it exceeds this threshold.
Since you're using Okta, it will provide whatever you have defined as a login (email for example) and Maximo will compare that against the loginid on the MAXUSER record. If you're still having issues in an InPrivate window make sure what Okta provides matches exactly what you have on their new user record.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Mon January 24, 2022 06:10 PM
From: Vandna Patel
Subject: User cannot login into Maximo using newly created User profile after Name change
Hello Everyone,
I have a user that had a name change. The new name has synced from AD into Maximo but she cannot login into Maximo using the new user id. I see the old name in the logs, even though the new userid is in Websphere as well as Maximo.
We are using OKTA for authentication and AD for user provisioning. Any ideas on where to look? We are on Maximo 7.6.1.2.
I appreciate your help in advance.
Thanks
Vandna
------------------------------
Vandna Patel
------------------------------