Obot Now Works with OneLogin: SSO and SCIM for Your AI Agents

Obot Now Works with OneLogin: SSO and SCIM for Your AI Agents

Obot now supports OneLogin as an identity provider. As of v0.28.0, you can sign users in to Obot with OneLogin single sign-on and provision users and roles automatically over SCIM. If your company runs OneLogin, you can put AI agents under the same identity system that already governs your people.

This one started with a partner. When we began working with Pentio, our partner in Japan, they told us many of their customers run OneLogin and asked if we could support it natively. Their engineers tested the integration with us as we built it. It is a good example of why we work with partners who live in identity every day. They know what an enterprise rollout needs before we do.

Why identity is the starting point for agent governance

Every company I talk to is rolling out AI agents. Developers are using Claude Code, Codex, and Cursor. Those agents connect to GitHub, Jira, databases, and internal APIs through MCP servers. The first question a security team asks is simple: who is this agent acting for, and what is it allowed to touch?

You cannot answer that with a separate user list. If Obot keeps its own copy of who works at your company, it is wrong the day someone changes teams or leaves. The identity provider is the source of truth. Agent access has to follow it.

That is what this integration does. Your OneLogin directory decides who can use Obot. Your OneLogin roles decide which MCP servers, models, and tools each person and their agents can reach.

What shipped

Single sign-on. OneLogin is now an authentication provider in Obot. You create an OpenID Connect app in OneLogin, give Obot the client ID, secret, and issuer URL, and your users sign in with the credentials they already have. You choose which OneLogin roles are allowed in. Everyone else is kept out.

Obot Now Works with OneLogin: SSO and SCIM for Your AI Agents

SCIM provisioning. OneLogin pushes users and roles to Obot as they change. You decide which users and roles Obot can see, and nothing else leaves your directory. With SCIM, Obot does not need an API credential for your OneLogin account at all.

Roles become groups. OneLogin roles show up in Obot as groups. You use them in access policies the same way you would with any other provider. Give the platform engineering role access to the production database MCP server. Give finance read-only access to the reporting tools. Set a monthly model budget for contractors.

Deprovisioning that works. When someone is unassigned or blocked in OneLogin, SCIM deactivates them in Obot. They are signed out, and their API keys and other credentials are disabled. Their account and data are kept, so restoring access brings back the same account. For a security team, this is the part that matters most. An agent should not keep working after the person behind it has left.

Identity passed downstream. Obot can pass the caller’s identity provider user ID and groups to MCP servers in trusted headers. Your backend systems can see who made a request, not just that an agent did.

What you get once OneLogin is connected

Identity is the foundation. Once it is in place, everything else in Obot keys off it:

  • Access policies for MCP servers, set by OneLogin role
  • An LLM gateway with access control, spending budgets, and content guardrails per group
  • Audit logs that tie every tool call to a named user
  • Obot Sentry on the laptop, so you can see which agents and MCP servers employees are running

One identity system for people and agents. One place to see what happened.

From our partner

Many of our customers already run OneLogin through Pentio. Being able to offer Obot with native OneLogin SSO and provisioning makes the story very simple: the same partner and the same identity platform, now extended to AI agents.

Haruhiko Hasegawa, Representative Director, Pentio Co., Ltd.

Pentio is one of the leading OneLogin partners in Japan and delivers Obot there with implementation, training, and first-line support in Japanese. If you are a OneLogin customer in Japan, they are the team to call.

Getting started

OneLogin support is available now in Obot v0.28.0 and later, and we recommend upgrading straight to v0.28.1. It requires a free Obot Community registration or an Enterprise license. The setup guide is in the docs at docs.obot.ai/configuration/auth-providers.

We already support Okta, Microsoft Entra ID, Google, Keycloak, JumpCloud, and Auth0. OneLogin customers now get the same first-class support. If you run OneLogin and want help connecting it, reach out. We would love to hear what you are building.

Related Articles