IBM Verify

Overview

IBM Verify is a managed identity and access management platform. It was formerly called IBM Security Verify. Its OpenID Connect application model can authenticate Pomerium users.

Using IBM Verify as the identity provider gives protected applications one sign-in path. Each application does not need to implement the same external authentication flow. Pomerium can apply route policy from the authenticated identity and request context.

IBM Verify sends authenticated identity data toward Pomerium. Pomerium uses that data with route policy. Pomerium then sends only approved application traffic toward the protected service.

How it works

Create an OpenID Connect application in IBM Verify. Prefer the current application template and discovery endpoint. Configure entitlements, attribute mappings, client credentials, and the exact Pomerium callback URL.

Configure Pomerium with the exact issuer or provider URL, client ID, and client secret. Use the Pomerium callback URL as an exact redirect URI. Request only the scopes and claims that access policy needs.

Test discovery, signing-key rotation, the authorization code flow, logout, and required claim mappings before production use. Keep provider credentials outside source control.

Example

A team registers Pomerium as an OpenID Connect client in IBM Verify. Users sign in through IBM Verify. Pomerium validates the identity response and applies route policy before it sends an approved request to a private application.

Considerations

• The older custom-application template can use a different legacy endpoint from the current OpenID Connect template.
• Entitlements and attribute mappings control which users and claims reach Pomerium.
• IBM Verify remains responsible for authentication, user lifecycle, and the identity data that it issues.
• A standards-based OpenID Connect pattern is not evidence of a vendor-specific connector or partnership.