HR, payroll and benefits · US and Canada

Lawson (Infor) as the source for Okta: joiners, movers, leavers.

StitchOps uses Lawson (Infor) as the source for Okta. New hires are in Okta before day one, job and manager changes update their access, and leavers are removed on their last day, with no HRIS API fee or custom development.

Book a free workflow audit Get a demo

HR Source pricing →

What's hard about Lawson (Infor) today.

Infor Lawson is common in healthcare and the public sector, and many organizations still run it on their own servers. Connecting it to Okta usually means file feeds and scripts, so new clinicians and staff wait for access and leavers keep it until the next cleanup.

What StitchOps does in Lawson (Infor).

Joiners in Okta before day one

When HR adds a new hire in Lawson (Infor), StitchOps creates them in Okta before their start date, so Okta can give them the apps their role needs on day one.

Role changes that update access

When Lawson (Infor) shows a new job, department, manager or location, StitchOps updates the person in Okta, and Okta adds and removes app access to match.

Leavers removed on their last day

When a last day arrives in Lawson (Infor), StitchOps deactivates the person in Okta, and Okta removes their access in every app it manages.

Email and username written back

Once Okta has the new person's email and username, StitchOps writes them back to their record in Lawson (Infor), so HR and IT see the same details.

Rehires, leave and contractors

Rehires get their original account back, people on leave are suspended and restored, and contractors follow their own rules.

On premises or in the cloud

StitchOps runs on a worker VM in your environment, so it can read Lawson where it is installed, without opening inbound ports.

Before and after.

The manual wayWith StitchOps

New hire added in Lawson (Infor)IT waits for an email, then builds the account.In Okta before day one, with the apps the role needs.

Role or manager changeNew access by ticket, old access forgotten.Okta updated, access matches the new role.

Last dayAccess removed when someone remembers.Deactivated in Okta, every Okta app follows.

Nightly file feed failsNobody notices until a new hire cannot log in.Every change logged, failures flagged.

What Okta covers for Lawson (Infor), and what StitchOps adds.

Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Lawson (Infor) account lifecycle.

Not in the Okta Integration Network.

StitchOps covers 8 of 8 capabilities for Lawson (Infor).

What Okta covers for Lawson (Infor), and what StitchOps adds
Capability	Okta, from the OIN	StitchOps
Single sign on	No SAML or OIDC in the OIN.	Enterprise password management signs users in to Lawson (Infor) with vaulted credentials. Users never need the password.
Shared accounts and MFA	Not part of the OIN listing.	Shares Lawson (Infor) logins and their MFA across a team, with credentials kept in your vault.
Joiners	No account creation in the OIN.	Creates the Lawson (Infor) account with the right role on day one, anywhere a person can log in and act.
Movers	No account updates in the OIN.	Changes Lawson (Infor) roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers	No deprovisioning in the OIN.	Removes Lawson (Infor) access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation	No password rotation in Lawson (Infor).	Changes the Lawson (Infor) password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews	No connector to read or remove Lawson (Infor) accounts.	Pulls the Lawson (Infor) user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence	Nothing logged inside Lawson (Infor).	Step level evidence for every action StitchOps takes in Lawson (Infor).

Single sign on
Okta, from the OIN
No SAML or OIDC in the OIN.
StitchOps
Enterprise password management signs users in to Lawson (Infor) with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Lawson (Infor) logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
No account creation in the OIN.
StitchOps
Creates the Lawson (Infor) account with the right role on day one, anywhere a person can log in and act.
Movers
Okta, from the OIN
No account updates in the OIN.
StitchOps
Changes Lawson (Infor) roles and access when someone changes jobs, anywhere a person can log in and act.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Lawson (Infor) access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
No password rotation in Lawson (Infor).
StitchOps
Changes the Lawson (Infor) password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Lawson (Infor) accounts.
StitchOps
Pulls the Lawson (Infor) user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Lawson (Infor).
StitchOps
Step level evidence for every action StitchOps takes in Lawson (Infor).

Okta coverage from the Okta Integration Network, read October 24, 2026. Lawson (Infor) has no OIN listing. StitchOps for Okta →

Common questions.

Do we need a Lawson (Infor) API or SCIM connection?

No. StitchOps reads hires, changes and terminations from Lawson (Infor) the way your HR team sees them. If your team already has a connection in place, StitchOps can use it instead.

Our Lawson runs on our own servers. Can StitchOps reach it?

Yes. StitchOps runs on a dedicated worker VM in your environment and connects outbound only, so it can read Lawson on your network without inbound ports.

What login does StitchOps need in Lawson (Infor)?

A login that can see hires, job changes and terminations, kept in your vault (1Password or Keeper) or the StitchOps vault. StitchOps runs on a dedicated worker VM in your environment, and models never see the credentials.

How is HR Source priced?

HR Source is priced per HR system per year, by company size, with no Lawson (Infor) API or SCIM fee on top. Prices are on our pricing page, and Connect for each app is priced separately.

How long does it take to connect Lawson (Infor)?

If StitchOps can log in to Lawson (Infor), it can often be connected in a day. A 30 day pilot can prove it in your own Okta before you sign.

Is Lawson (Infor) in the Okta Integration Network?

No. As of October 24, 2026, the OIN has no listing for Lawson (Infor). Okta can sign users in only through a custom app if Lawson (Infor) supports SAML or OIDC, and has no connector to manage Lawson (Infor) accounts.

Can Okta deprovision Lawson (Infor) users?

Not through an OIN connector. StitchOps removes Lawson (Infor) accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.

How do you rotate Lawson (Infor) passwords when someone leaves?

StitchOps logs in to Lawson (Infor), sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.

For your IT team

Where it runs: An agent runs an unattended desktop session on a dedicated worker VM in your environment, on Windows or macOS. It connects outbound only over TLS 1.2 or later. No inbound ports are opened.
Credentials: Credentials stay in your vault (1Password or Keeper) or in the StitchOps vault, encrypted with AWS KMS and resolved on the worker at run time. Models never see the values.
Okta stays the source of truth: StitchOps creates, updates and deactivates people in Okta from your HR system, and Okta Lifecycle Management carries the change to every app. StitchOps is listed in the Okta Integration Network.
Logs and telemetry: Every run keeps step level logs with status, timing and redacted results. Telemetry is content free: no field values, no personal data, no screenshots.
Security reviews: SOC 2 Type 2 examination completed, with HIPAA and GDPR Article 5 attestations, by Sensiba LLP. Penetration tested by a third party. ISO 27001 certification being finalized. The security packet is shared under NDA.

Last updated October 24, 2026. Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.

See it run in your Lawson (Infor).

Fifteen minutes on how Lawson (Infor) reaches Okta today. We show you joiners, movers and leavers running from it.