AUTHIVOR

Authivor · for Oracle E-Business Suite 12.2

Every person through the right door.

Who is signing in?

Pick a person

User

anna.berg

Network

Office · 10.10.4.21

Group

Staff

Organisation

Finance

group is Admins

→ Entra ID + strong MFA

no

group is Contractors

→ Okta + MFA

no

group is Suppliers

→ Auth0 + MFA

no

group is Applicants

→ Google sign-in

no

network is Office

→ Keycloak, SSO

match

Anna, staff → Keycloak · single sign-on

A demonstration of how routing rules decide: the first match wins, and the rules below it are not checked. Only Keycloak is proven in our lab; the other providers show where a rule can send someone. It changes only this page.

Staff, contractors, suppliers, applicants and admins all sign in to one ERP. Authivor sends each of them to the right identity provider, checks your own directories and databases, and decides. Your team writes it in lines it can read, preview and undo.

A Nessort product. Shown with made-up people from our lab.

In our lab

Real systems. Made-up people.

Everything on this page was proven on a lab built like a real company: the Oracle Vision demo of E-Business Suite, a real Active Directory and the databases a business keeps beside its ERP.

In the lab, a small module in EBS's own web server (Oracle HTTP Server) sends sign-ins to Authivor. Authivor runs the OpenID Connect sign-in, decides, and opens the EBS session for the mapped EBS user. EBS keeps its own users and responsibilities.

Oracle E-Business Suite 12.2Vision, behind Authivor's gate
Active DirectoryWindows Server 2025, over LDAPS
Keycloakthe identity provider, over OpenID Connect
SQL Server 2022HR: who is active, who is on leave
MySQL 8.4the SOC's own watchlist
PostgreSQL 17training records
8.7 msfor the decision itself with 200 rules in force, at the 99th percentile; live checks to AD, HR and databases add their own time.
41 of 41attempts to run anything but one read-only SELECT in a database check, refused before they ran.
71 of 71recorded decisions replayed offline with exactly the same answer.

Watch Authivor open the right doors.

3 minutes 36 seconds, narrated, with captions.

Read the transcript

Every morning, thousands of people need to get into your ERP. Employees in the office. Contractors at home. Suppliers on the web. Job applicants. Administrators on VPN. Each one different. Each one needs the right door, and your team has to open it, securely, every time.

What if all of that fitted in one sentence your team can read?

That's Authivor. Every line has three parts: what to do, what it acts on, and when it applies. One word opens every action. One object covers people, directories, databases and networks. One rule mixes them however you need.

Authivor reads who is signing in and sends each person to the right identity provider, with the right strength of proof. Anna goes straight in with single sign-on. Karim, a contractor, goes through Okta with MFA. Maria from a supplier, Jun applying for a job, Sara the admin: each one gets their own door, from one set of rules.

Authivor checks the systems you already trust: Active Directory, HR, your SOC, Oracle EBS itself. Every answer is a simple yes or no, so a decision is never a guess.

And soon, you won't need to learn the syntax at all. Say it in English. The AI compiler writes the line, and Authivor checks it before anything happens.

Connect a directory or a database in one line. Passwords and certificates stay in Authivor's own vault, by name. Every change shows its effect before it's applied, every version can be restored, and every decision is recorded.

The right people, through the right door, the moment they need it.

Authivor. Your ERP, your rules, one line. Part of the Nessort family, with Ordivor and Assertor. All our products at nessort.com/products.

Verb. Object. Rule.

Every Authivor line has the same three parts, in the same order: what to do, what it acts on, and when it applies. Pick a part to see what it opens.

In plain words: explain what the directory ad-main reads, and which checks use it.

Five lines your team will use.

/directory createConnect

Connect your directories and databases.

Add as many as you need: Active Directory or LDAP over an encrypted connection, and Oracle, SQL Server, MySQL or PostgreSQL. Their passwords and certificates go into Authivor's own vault, under a name you choose, and are never shown again.

One line connects a directory

/directory create ad-main url="ldaps://dc1.northwind.test:636" bind_password.$secret.provider="store" bind_password.$secret.name="ad-bind" activate=true

The password, set once in the vault

ad-bind••••••••••••tested

/create @authivor.routingRulesRoute

Send each person to the right door.

Routing rules choose which identity provider proves who is signing in, and how strongly: single sign-on for staff in the office, MFA for contractors and suppliers, strong MFA for admins. Rules are checked in order and the first match wins, as in the demo at the top.

Proven in our lab

Keycloak · OpenID Connect

Same standard, to be confirmed in a pilot

Microsoft Entra ID, Microsoft AD FS, Okta, Auth0, Google, Oracle Access Manager, OCI IAM Identity Domains, PingFederate.

/explainDecide

Ask the systems that know.

At sign-in, Authivor asks your directory, your HR database, your SOC and Oracle EBS itself. Each check is one read-only question with the user bound in safely, and it answers yes or no.

Checks for anna.berg, at sign-in

In Finance, nested groups includedActive Directory · LDAPyes
Active, not on leaveHR · SQL Serveryes
Clear on the SOC watchlistSOC · MySQLyes
Holds the GL responsibilityOracle EBS · SQLyes
From the office or VPNNetwork · 10.10.4.21yes

say itIn English

Say it in English.

Your team doesn't have to learn the syntax. Describe the change in plain words and the AI compiler writes the line. Authivor's own parser checks it, and when a request could mean two things, it asks.

IN DEVELOPMENT

You say

Contractors sign in through Okta, with MFA.

Authivor writes

/create @authivor.routingRules set id="R-OKTA", when='groups contains "Contractors"', then.provider="okta", then.min_assurance="mfa"

/apply · /authivor replayPreview and prove

See the effect first. Keep the proof after.

Every change runs first as a dry run against real recent sign-ins, so you see who it would affect, by name. One /apply makes it live, and every earlier version is kept. Each decision and change lands in a chained evidence log with the facts it was decided on, and can be replayed offline later with the same answer.

Dry run of the Okta route

1 sign-in changes routekarim.nabil → Okta + MFA

/apply p-7c41e09a2bd35f18

Replay, with the network switched off

/authivor replay ev-77ed16ecfbe81308 config=current

exact · recorded ALLOW, replayed ALLOW

Every person through the right door.

Authivor, by Nessort. Proven in our lab with made-up people.

For IAM and SOC teams

If your team looks after staff, contractors, suppliers and applicants on one Oracle EBS, we would like to show you Authivor on your own scenarios and hear how sign-in works at your company today.

For investors and partners

Authivor grows out of Nessort's work in identity architecture and assurance, beside Ordivor and Assertor. If you would like to follow it or build with it, write to us.

Write to Nessort info@nessort.com
AuthivorWho gets into Oracle EBS, and why.You are here
OrdivorChange access across every system. One AI helps you write the plan, another checks it, a person decides.
AssertorThe evidence layer: who can do what, since when, and who says so.

All products · nessort.com/products

AUTHIVOR A Nessort product Nessort