Choose your country or region

Okta for your bank's staff portal, with provisioning.

Staff sign in with Okta, Okta groups decide what they can do, and a deactivation in Okta ends their access in the portal straight away. Everbranch builds small and medium banks their banking app and staff portal; your staff sign in to the portal with Okta.

The connector for Okta is built and ready to configure for your bank.

Staff sign-in

How we connect to Okta

Okta is an identity platform many organisations use to sign their workforce in to applications. An Okta app integration can sign people in over SAML 2.0 or OpenID Connect, and Okta provisions users and groups into applications over SCIM 2.0, including Group Push and deactivation with active set to false.

SAML 2.0 or OpenID Connect

Your Okta admin creates an app integration for the staff portal; your bank admin registers it with us, and every response is checked for signature, audience and replay.

SCIM for users and Group Push

Okta creates, updates and deactivates staff over SCIM 2.0, and pushes groups and their members, with a token your bank admin issues.

Groups to roles, under your control

Your bank decides which Okta group grants which role; changing the mapping needs a role administrator, so nobody grants themselves access.
Data

What moves between Okta and your app

  • Signed sign-in responses, checked and turned into a staff session
  • Name, work email and groups for each staff member
  • New users, profile changes and group membership over SCIM
  • Deactivations that end the person's sessions at once
  • Forced re-authentication through Okta before sensitive actions

Passwords, Okta Verify and your sign-on policies stay in your Okta org. Staff provisioned over SCIM never get a password with us.

Use cases

What your bank can do with it

Give a new hire the right access on day one

Assign them to the right Okta group and their portal account and role arrive by SCIM.

Separate makers from checkers

Map payment makers and approvers to different groups, and the portal's segregation-of-duties rules do the rest.

Close access fast in an incident

Deactivate a person in Okta, or disable the whole provider in the portal, and the sessions it issued end.
Why it matters

What it changes for your bank

Your sign-on policies, unchanged

Multi-factor and device rules you set in Okta apply to the staff portal like any other app.

Nobody locked out

Break-glass admins keep a separate password and authenticator, and the last active provider can't be switched off under single sign-on only.

Every change on the record

Sign-ins, provisioning changes and role syncs are written to your bank's audit trail.
Rollout

From first call to live

  1. Step 1: Create the Okta app integrationYour Okta admin chooses SAML 2.0 or OpenID Connect and enters the addresses from your admin console.
  2. Step 2: Map groups to rolesYour bank admin decides which Okta groups grant which staff roles, and which email domains to trust.
  3. Step 3: Turn on SCIM provisioningYour bank admin issues a SCIM token, and Okta starts creating staff and pushing groups.
  4. Step 4: Move to single sign-on onlyOnce staff sign in through Okta without trouble, you switch off passwords for everyone but break-glass admins.
Questions

Okta: what IT teams ask

Is the Okta connection an Okta-certified integration?
No. It works through the standards Okta supports: SAML 2.0, OpenID Connect and SCIM 2.0. We tested it against standard mock providers, not certified by Okta, and you create it as your own app integration.
Does Okta Group Push work with the staff portal?
Yes. Pushed groups and member changes arrive over SCIM, and your bank's group-to-role mapping decides what each member can do. Role changes over SCIM apply at once.
Can Okta step-up protect approvals in the staff portal?
Yes. Before sensitive actions the portal can send the person back to Okta for a fresh sign-in, and checks it is the same person signing in after the request.
Can we run Okta and passwords side by side while we test?
Yes. Your bank can allow both while staff move over, then switch to single sign-on only. Break-glass admins keep their password either way.
Related

Microsoft Entra ID

Your staff use the work account they already have. Entra ID signs them in, your groups decide their roles, and leavers lose access the moment you switch them off.
Microsoft Entra ID integration

Salesforce

Your relationship managers work in Salesforce. Your customers bank in your app. We keep the two in step, so nobody re-types an application or misses a complaint.
Salesforce integration

Apache Fineract

Your customers open accounts, check balances and pay from one app in your brand. Fineract stays your book of record, and our connector talks to it through its REST API.
Apache Fineract integration
Pilot programme

Running Okta? Let's map it.

Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment