How-toInfor LNWeb UI / Infor OS / Administration

Infor LN Session Timeout, Starting Sessions and Personalization

Question
infor ln session timeout

Also searched as

  • infor ln start session
  • infor ln session personalization
  • infor ln web ui idle timeout
  • infor ln open session by code

Short answer

An LN user can lose a session for two different reasons: the portal or identity token expiring (Infor OS or the identity provider) or the LN application server dropping an idle process. Check the identity token lifetime first, then server-side idle settings. Sessions are started by typing the session code in the Web UI search, and personalization is done per user or per role with the built-in personalize options.

Applies to: Infor LN 10.x Web UI with Infor OS (Ming.le) or a customer identity provider. Settings differ between cloud and on-premise.

How to diagnose and set timeouts

  1. 1Note exactly what the user sees: a login prompt (token expiry) or a frozen session (server side).
  2. 2Check the identity provider or Infor OS configuration for the session or token lifetime and the idle limit.
  3. 3On the LN application server check the settings that end idle sessions or limit the number of concurrent sessions.
  4. 4Check network devices: load balancers and firewalls often close idle connections earlier than the application does.
  5. 5Set the shortest limit that suits your security policy and announce it, so users know what to expect.
  6. 6Re-test with a user left idle for just over the new limit.

Starting a session by code

In the Web UI you can open a session by typing its code, such as the code of a purchase or item session, into the search or run box and selecting the result. Power users prefer this to navigating menus. In the classic client a similar run-program option exists.

Sessions can also be added as favorites or opened by a link from other applications. Make sure the user holds authorization for the session, otherwise the start fails with a not authorized message.

Session personalization

Personalization lets a user or admin change how a session looks: which columns appear, their order and widths, and saved filters or views. Keep personalization for layout. Changing behavior needs a customization with a proper change record.

Decide who owns shared views. If every user personalizes their own, support cannot reproduce what a user sees.

Security trade-offs

Long timeouts are convenient on the shop floor but risky on shared terminals. A common compromise is a short timeout for office users and a longer or badge-based re-entry for shared stations. Align it with your policy rather than with whatever stops complaints.

Try it here, free

Infor LN Session Test Script Template

Open full tool

UAT test script for an LN process or session with prerequisites, numbered steps, expected results and tester sign-off.

Common pitfalls

  • !Raising only the LN limit while a load balancer still closes the connection.
  • !Mixing up token expiry with server-side idle handling.
  • !Leaving shared terminals on long timeouts.
  • !Using personalization to change behavior.

How an ERP-grounded AI assistant handles this

Netray's agent can read session and login logs from your environment to explain why a user was dropped and which layer did it. It does not change security settings by itself; any change stays with your administrators.

Frequently asked questions

Why is my LN user logged out while working?

Most often the identity token or portal session expired, or a network device closed an idle connection. Check the identity layer and the network before changing LN itself.

How do I open an LN session by its code?

Type the session code into the Web UI search or the run option and open the result. The user needs authorization for that session.

Can personalization be shared with other users?

Yes in many setups at role or admin level. Decide who owns shared views so that support knows what users see.

Does a longer timeout affect license use?

It can, because idle sessions may still hold a license until they end. Check your license model.

Related

Error fix

Infor LN Not Authorized to Run This Session: How to Fix It

Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.

Error fix

Infor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It

A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.

Error fix

Infor LN 'unable to create a session': causes and how to fix it

This message means the client reached LN but the server could not start the session process (a bshell) or could not load the session. Work from the server side: check the bshell log, licence and user limits, the user's authorizations, and whether the session or its dependent objects exist and are compiled.

Error fix

Infor LN DAL Out of Sync After a Custom Field: Cause and Fix

Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.

Error fix

Infor LN Jobs Stuck in Active or Waiting: Fix the Job Daemon

Infor LN background jobs, reports, batch processes and print jobs, get stuck in Active or Waiting status when the job daemon on the enterprise server has stopped or lost its connection, or when a prior job crashed without releasing its status. Restart the job daemon and reset the stuck job's status through the Jobs session, and the queue resumes. A daemon that keeps stopping usually points to a memory, license or database connectivity problem on the server.

Error fix

Infor LN Reports Stuck in the Print Queue: Device and Spooler Fix

Infor LN reports and forms stay queued and never reach the printer when the target device definition points to a printer that is offline, or the print listener on the print server has stopped. Check the device's status in Common > Printing > Devices, confirm the underlying OS printer is reachable, and restart the print listener if jobs remain queued after the printer itself is fixed. Most cases trace back to a genuinely offline printer, not an LN bug.

AI for ERP

AI for Infor LN: Sessions, BODs, and Engineer-to-Order Work

Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.

AI for ERP

AI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door

Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.

Stuck on Infor LN?

Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations