Lawson Security Administrator Stuck on Authenticating after two-factor sign-in

, ,

When running Lawson Security Administrator (LSA), you may get stuck on the authentication screen even after going through the two-factor sign-in. Here is how to resolve this issue.

 

Run LSA as Admin and login

Ping ID Authenticates

 

Script Error pops up, clicking yes, no or closing leads to same result:

Doesn’t connect after:

LSA Logging gave me these results 9/20 when last tested (logs not updating now):

LSA Version 10.0.3.01065

 

Installing LSA Version 10.0.3.01069 Resolves this issue. And that’s it!

IPD Debugger Feature

, ,

IPD  enables you to debug your processes. To activate the Debug view, go to the Infor Process Designer menu bar and select Window > Show View > Other

From there select Infor Process > Debug and click on OK.

The Debugger feature set includes:

  • Breakpoint management- can be enabled for any activity node within a process, and causes a running process to pause at the point before the specified activity node. When the process pauses, process variables can be examined and/or modified. Process execution can be resumed at the breakpoint, or at any other activity node if desired.

To set this up, right mouse click on the node to debug and select Debug

The Run to this activity breakpoint is temporary and only valid for the current execution of the process. A “run to” breakpoint can be useful when you want to pause at a specific activity node during the current execution, but you do not want it to stay in effect for any subsequent executions. All temporary breakpoints are cleared before a process starts execution.

This feature is available only when running the process locally.

  • Process execution controls

The run process control starts the execution of a process and is available if the process is currently not running or paused. The Run Mode option gives you the option to run the process either locally or on the server. The flow can be run on the server from the designer and provide you with the status and log information.

Specify Input data can be used to pass data to a process. The data will be added to the workunit once the workunit has been created. You can select from these options when specifying the input data:

  • No input data: Select this option if you do not want to pass any specific data to the process.
  • Use data from Workunit: You must specify the workunit number. The process will fetch the input data from that workunit and use the same data in the current process. If the workunit or input data does not exist, then the input data will be null.
  • Use connector: You can select between two options. The first one is Specify input data where you can specify the data that you want to pass to the process. The second is Input data file where the data will be read from the given file and be used in the process.
  • Runtime variable examination and modification

This feature is available only when running the process locally (that is, Run Mode is set to Local).

Once a running process is paused at an activity node, the current value of variables in the process can be examined and modified if needed.

The Debug view shows a list of currently running processes. The variables accessible to the activity node at the pause point is shown, organized by variable category and activity node. Selecting a variable shows its current value, and a new value can be specified.

5 Patching Tips in Lawson v10

, ,

These 5 tips could make applying patches that much less stressful and are also good practice in general.

 

Tip 1: Check existing patch logs to see if a patch has already been applied previously and current versioning. This is good to check after a patch has been applied as well.

These logs can be found and generated here in LID:

perl %GENDIR%\bin\patches_installed_report <productline>

perl %GENDIR%\bin\source_versions_report <productline>

 

Tip 2: Restart the LSF server (or services) to ensure no processes are being held up and when it boots up, turn off Websphere LSF Appserver service before applying a patch to ensure users cannot log on, especially if patch needs to be applied during or close to work hours.

 

Tip 3: Run dbdef command to make sure there is a connection to the database before patching

 

Tip 4: When activating or staging multiple patches, run this command to speed up the post compile process:

qcontrol -jlocal,4  – This will set the servers cores to 4 when processing form compiles. Set it back to 2 when done. You can also check the status of the compiled jobs with command: qstatus | head -5

 

Tip 5: If a Plus dictionary is created after patching, its typically good practice to compile the entire product line with the command: cobcmp (be aware this can take up to 20-30 minutes to complete, tip 4 helps with this). This ensures that all programs are functioning correctly before passed to testers.

 

Bonus Tip: Verify security is on before sent to the testers!  Hope these were helpful.

 

If you found this article helpful, Nogalis provides managed services and expert technical resources to assist with Lawson patching and system maintenance. If applying patches feels overwhelming or time-consuming, our team can simplify the process by managing everything from version checks to database connectivity and post-compile optimizations. Let us help ensure your patches are applied efficiently and your system is running smoothly. Contact us to learn more about how we can support your Lawson environment.

Lase_server indicates a message is too large

, ,

The message “lase_server logging issue – Invalid message is received and size” indicates that an error message that is too large has been sent from the security server.

Example full message text

default.SEVERE server.SecurityEventHandler.run(): SecurityEventHandler #816 got exception. com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=64706,localport=450000].

Stack Trace : com.lawson.security.server.LawsonNetException: Got exception while reading from connection Socket[addr=/127.0.0.1,port=6406,localport=50000].

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:339)

at com.lawson.lawsec.server.SecurityEventHandler.run(SecurityEventHandler.java:151)

Caused by: java.io.IOException: Invalid message is received and size:300095616

at com.lawson.security.server.AbstractDefaultEventSource.readMsg(AbstractDefaultEventSource.java:351)

at com.lawson.security.server.AbstractDefaultEventSource.read(AbstractDefaultEventSource.java:352)

 

Resolution

The parameter server.readMsgMaxSize must be added to lsservice.properties.

The MsgMaxSize parameter ensures that a logging message that occurs when a vulnerability scan is run does not become so large that it causes the system to hang. The parameter catches very large messages and replaces them with shorter sample messages.

Perform these steps to add the parameter.

  1. Stop the Infor environment and the application server.
  2. Open the lsservice.properties file for editing.
    On Landmark, the location is: LASYSDIR/lsservice.properties
    On LSF, the location is: LAWDIR/system/lsservice.properties
  3. Add the parameter server.readMsgMaxSize=[size number in Bytes] to the end of the file. The default size is 20MB. Infor recommends not setting the size larger than 40MB.
    Example: server.readMsgMaxSize=20
  4. Restart the Infor environment and the application server.

 

Lawson Security Administrator Stuck on Authenticating after two-factor sign-in

, ,

Note that the below information is reproducible on a cloud client via jumpbox or local PC connected to VPN.

 

If your Lawson Security Administrator is stuck on authenticating after two-factor sign-in, follow these steps to reproduce and get a solution (this is to make sure you’re experiencing the same issue):

Run LSA as Admin and login.

Ping ID or Two-factor equivalent Authenticates

Script Error will pop up. Clicking yes, no or closing the window leads to the same result:

Doesn’t connect after, stuck on Authenticating.

This occurred on LSA Version 10.0.3.01065 in a Infor Cloud Environment.

 

Resolution:

Installing LSA Version 10.0.3.01069 Resolves issue and LSA is able to authenticate after the two-factor.

 

Adding Context Apps in Infor OS Portal

, ,

Follow the steps below to add a new context app in Infor OS Portal.  In this example, we will enable the app for Infor Lawson S3.

Log into Infor Portal and Click on User Settings > Admin Settings

Go to the Manage Context / Utility Apps tab and select “ADD CONTEXT/UTILITY APP”

Enter a Type, Name, Description, and URL.  Click Save.

 

Now, add the application(s) that will be using this context app.  At the bottom of the screen, select the Applications tab and select “Add/Remove Applications”.

Select the application(s) and click Done

Be sure to Enable to application and then click “Save”

Your context app now shows up in the right side menu

 

How to preserve linked Lawson tables in Access when copying to different machines

, ,

Need an Access Lawson database to reside on the desktop of select users without having to relink all the tables each time?

If so, see the below query for the DSN-less connection with a function to relink all the tables and pass-through queries. This also just works for databases in general. Good luck!

 



 

If this process seems too complex or time-consuming, Nogalis offers expert managed services to help you manage and optimize your Lawson databases, including handling table linking and other database configurations. Whether you’re looking to simplify data management across multiple machines or improve overall system performance, our team can provide the support you need—without the overhead of a full-time, in-house staff. Contact us to learn more about how we can assist with your Lawson environment.