Oracle Identity and Access Management. How it is licensed.

Oracle identity and access management is not one product. It is a family that spans Oracle Access Manager, Oracle Unified Directory, and Oracle Identity Governance, each licensed on its own metric. The trap is assuming a single entitlement covers the whole stack.

This guide is for Oracle administrators and procurement teams sizing Oracle identity and access management in 2026. Read it with the Oracle Access Manager licensing guide, the Oracle Fusion Middleware licensing guide, and the Oracle Practice page.

What does Oracle identity and access management include?

The IAM family groups several products that solve different problems. You license the ones you deploy, not the suite as a whole, unless you have bought a suite bundle on purpose.

Which products sit in the IAM stack?

The common components each address a distinct function, from authentication to directory services to governance.

• Oracle Access Manager: single sign on and web access control.
• Oracle Unified Directory: the LDAP directory and storage layer.
• Oracle Identity Governance: provisioning, certification, and access requests.

What metrics do the IAM products use?

Most IAM components license on processor or named user plus, the same two metrics used across Oracle technology. The choice between them follows your user count, just like the database. Oracle publishes the definitions in its software licensing documentation.

How do you size and price an IAM deployment?

The cost depends on which components you run, the metric you pick, and the hardware they sit on. Get those three right and the rest is arithmetic.

How does the core factor change the processor count?

IAM processor licensing uses the Oracle core factor table, so the same physical cores can map to a different license count by chip type. The Oracle core factor explained guide shows how the multiplier works in practice.

Where do buyers overspend on IAM?

The most common waste is licensing the full suite when only two components run in production. Map your real deployment first, then license to it, rather than buying the bundle for cover you do not use.

IAM is sold as a family, so it is easy to buy the family. The buyer side move is to license only what runs in production, on the metric that fits your user count.

What to do next

1. List every IAM component you actually run in production today.
2. Confirm the license metric on each one against your current contract.
3. Count processors with the correct core factor before you accept a quote.
4. Compare processor against named user plus for each component by user count.
5. Drop any suite cover you bought but never deployed.
6. Check that disaster recovery and test environments are licensed correctly.
7. Re verify the metric mix before any renewal or hardware refresh.

Frequently asked questions

Is Oracle identity and access management one license?

No. Oracle IAM is a family of separate products, each with its own license metric. Access Manager, Unified Directory, and Identity Governance are licensed individually unless you have negotiated a suite bundle that names them together.

What metric does Oracle IAM use?

Most IAM components license on processor or named user plus, the same two metrics used across Oracle technology products. Processor suits large or external user populations, while named user plus can be cheaper for small, countable internal teams.

Does the core factor apply to IAM licensing?

Yes. Processor based IAM licensing uses the Oracle core factor table, so the license count depends on the chip type as well as the core count. Always apply the correct factor before you size a processor based deal.

Is there a named user plus minimum for IAM?

Yes. Named user plus carries a per processor minimum that you must meet regardless of your actual user count. On larger hardware that minimum can make processor licensing the cheaper option, so model both.

Should I buy the IAM suite bundle?

Only if you deploy most of the components. A suite bundle pays off when you run the full stack, but it wastes money when only two products are in production. Map your real deployment before you accept a bundle.

How do you reduce Oracle IAM licensing cost?

License only the components you run, on the metric that fits your user count, and drop unused suite cover. Verifying the core factor and named user plus minimums before signing prevents the two most common IAM overcharges.