How to debug login issues in Lawson with SAML Tracer Tool
When logging into Lawson via a federated system and SAML configuration, a SAML response is received from Azure and that is all Lawson cares about when authenticating.
Users may see an error like this if the ID differs from the SAML configuration:
Authentication Failure
Unable to create a session. Contact your system administrator and provide this information along with the tracking id:
<long hash code ID for Infor to debug>
How to debug:
Once you’re in Lawson, any app issues are related to Lawson internally.
- Add SAML Tracer: Browser extension to chrome
- Open the SAML Tracer
- Login to Lawson and export the SAML Trace:
- Open the json or XML file in Notepad++ and search for <NameID Format=
- Search for your known user name:
That’s it! This is what is being returned from SAML response on the Azure side. You’ll have to work with the network team to coordinate on the proper ID for the user to use in Lawson.
Retiring Lawson, PeopleSoft, or Oracle? APIX archives the entire application — every table, every year, attachments and security included — into your own AWS account in about 30 days, so you can decommission the legacy system and keep full access to the history.
