Agentless Okta SSO

INTEGRATIONS · OKTA SSO

Agentless / People and AI agents

One identity
for people and agents.
Enforced everywhere.

Okta signs in your people. FS Sentry and QS Platform 10 carry that identity to every API, document and AI agent, so agents, like employees, can reach only the corporate artifacts their job requires.

Agentless Okta SSO for your APIs, with every OAuth interaction handled for you, and any-to-any token translation across subsidiaries, partners and legacy systems. No agents or coding required.

In production with QS Cortex: authentication and authorization at the document and agent level.
OKTA · FS SENTRY · QS CORTEXSSO
FSSentry

Authenticate

Okta · SAML · OIDC

Authorize

Tools · docs · APIs

Translate

Any token to any

Agentless · No user-based fees · FIPS 140-2 · Common Criteria NDPP
Employees
Sign in once
AI agents
Inherit entitlements
Partners & subsidiaries
Their own IdPs
An agent never sees more than the person it works for.
ONE IDENTITY.
EVERY CALLER.
Agentless Okta SSO

Built-in adapter handles every OAuth interaction

Agents restricted like employees

Tool, document and API authorization

Any-to-any tokens

Across subsidiaries, partners and legacy systems

01

AGENTLESS OKTA SSO

Okta SSO for your APIs,
without agents or code.

FS Sentry includes a built-in Okta adapter for SSO and multi-factor authentication, so you don’t deploy a separate identity agent on clients or services. It generates, consumes and verifies SSO tokens, and handles every OAuth interaction for you.

No identity agents.

Legacy IAM tools need agents and adapters on every application, with rip-and-replace effort to match. FS Sentry enforces Okta SSO in the gateway instead.

SSO, MFA and continuous authentication.

Enforce two-factor, multi-factor and multi-context authentication, and keep verifying identity on every call rather than only at sign-on.

Okta, or the IdP of your choice.

Prefer another provider for MFA and authentication? FS Sentry enforces SSO and continuous authentication with built-in integration to the identity solution you choose.

02

IDENTITY FOR AI AGENTS

Agents are colleagues.
Give them the same boundaries.

In QS Platform 10 deployments with QS Cortex, Okta is a critical part of agent security, for both authentication and authorization. When an employee asks an agent for help, the agent works on that employee’s behalf, with the same identity and groups, so it can reach only what that employee could reach.

OktaWorkforce sign-on, MFA, groups and attributesthe same identity and groups travel with every stepEMPLOYEESigns in oncewith Okta SSOAsks an agentfor helpQS CORTEX AGENTActs on behalfof that employeeNever more accessthan the personQS DevX entitlementsWhich tools the agent may useDocument access controlOnly documents the user may seeFS Sentry authorizationEvery API call checked by policyCORPORATE ARTIFACTSAPIs and systems of recordContracts and policiesRecords and documentsAuthenticated at sign-on · authorized at the tool, document and API level · audited end to end
Conceptual flow. Entitlements, document permissions and API policies are configured per deployment.
AUTHENTICATION

Signed in once

Employees authenticate with Okta. Agents act under that authenticated identity, never under a shared service account.

TOOL LEVEL

Entitled tools only

QS DevX entitlements decide which tools each agent may discover and use, based on the user’s groups and role.

DOCUMENT LEVEL

Only permitted documents

Agents retrieve and reason over only the contracts, policies and records the employee is allowed to see.

API LEVEL

Every call authorized

FS Sentry checks each agent API call against policy, with least privilege, rate limits and full-context logs.

THE NEED-TO-KNOW PRINCIPLE

Agents, like employees, should be restricted to the artifacts their job requires.
With Okta and QS Platform 10, that restriction is enforced at sign-on, at every tool, every document and every API call.

03

CENTRALIZED CONTROL, MULTIPLEXED IDENTITY

One control point
for every identity pattern.

Real enterprises don’t run on one identity system. Business units, subsidiaries, partners, SaaS providers and decades-old applications each speak their own protocols and token types. FS Sentry sits in the middle as one policy point, verifying whatever arrives and issuing whatever the destination expects.

FS SentryOne identity control pointVerify · translate · mapany token to any tokenWorkforceOkta · OIDC · SAMLAI agentsDelegated user identitySubsidiariesTheir own identity providersLegacy systemsWS-Security · Basic · customCloud and SaaSOAuth · JWT · OpenID ConnectPartnersClient credentials · mTLS · SAML
Illustrative. Each party keeps its own identity provider and token format; FS Sentry verifies, translates and maps between them under one policy.

INSIDE THE ORGANIZATION

Workforce, agents and legacy systems.

Okta identities flow to modern APIs as OAuth or JWT, to older services as WS-Security or SAML assertions, and to AI agents as delegated identity, without changing the applications.

ACROSS SUBSIDIARIES

Federate without forcing one IdP.

Subsidiaries and acquired companies keep their own identity providers. FS Sentry federates them with any SAML profile, OAuth grant type or WS-Trust, and maps their attributes to shared policies.

WITH OUTSIDE PARTIES

Partners on your terms.

Partners and SaaS providers connect with client credentials, mutual TLS or signed SAML. They never see internal tokens, and you never share credentials.

Why centralize? One place to change identity policy, rotate certificates and audit access, instead of a different integration in every application, subsidiary and partner connection.

Zero trust architecture
04

TOKEN AND PROTOCOL COVERAGE

Virtually every identity token,
legacy and modern.

Built-in support for identity token formats lets every architecture component, old and new, take part in the SSO paradigm. Lower costs, with no user-based fees.

Authentication formats

Any-to-any conversion: HTTP Basic, Form Post, Digest, PKI, WS-Security tokens, SAML, OAuth, JWT, OpenID Connect and adaptable custom tokens

Identity provider services

SAML token service, OAuth token service and WS-Trust security token service

Service provider initiated

SAML Web SSO, OAuth redirect, web redirect and user-defined workflows

Authentication

Two-factor (2FA), multi-factor (MFA) and multi-context authentication (MCA)

Federation

Any SAML profile, any OAuth grant type, WS-Trust and XML digital signatures

SSO

Identity attribute caching, cookie management and session management

Agent identity

Delegated user identity for QS Cortex agents, tool entitlements and document-level access

Auditing

Transaction audit trail with machine learning–ready log formats

05 · HYBRID ON-PREMISES AND CLOUD

Identity across every boundary.
Cloud and on-premises.

FS Sentry unifies external integration points around a central architecture, translating protocols and message formats to match cloud requirements while supporting the identity standards of both cloud and legacy systems.

Integrations are repeatable and scalable, with minimal coding and minimal disruption, secured by FIPS 140-2 and Common Criteria NDPP technology.

Agentless MFA

THE DETAILS

Questions,
answered.

Okta SSO, identity for AI agents and federation across organizations.

How QS Cortex runs agents
Do we need to install Okta agents on our applications?

No. FS Sentry includes a built-in Okta adapter and handles OAuth interactions in the gateway, so no identity agents are deployed on clients or services.

How do AI agents use Okta identity?

In QS Platform 10, a QS Cortex agent acts on behalf of the signed-in employee, using that employee’s Okta identity and groups. QS DevX entitlements limit its tools, document access control limits its documents, and FS Sentry authorizes every API call.

Can agents see documents the user can’t?

No. Document-level access control restricts agents to the documents the user is permitted to see, the same need-to-know boundary that applies to employees.

Our subsidiaries use different identity providers. Is that a problem?

No. FS Sentry federates multiple identity providers with any SAML profile, OAuth grant type or WS-Trust, and maps their attributes to shared policies, so each organization keeps its own IdP.

Which token types does FS Sentry support?

Virtually all of them, including HTTP Basic, Form Post, Digest, PKI, WS-Security, SAML, OAuth, JWT, OpenID Connect and custom tokens, with any-to-any conversion between them.

Can we use an IdP other than Okta?

Yes. FS Sentry integrates with the identity solution of your choice, including Microsoft Active Directory, Ping and LDAP directories, and enforces SSO and continuous authentication the same way.

OKTA SSO · QS PLATFORM 10

One identity for people and agents.
Enforced everywhere.

See how FS Sentry and QS Platform 10 extend Okta to every API, document and AI agent, without agents or code.