Service

Identity & Access Management

Secure sign-in and authorization for your applications: single sign-on, multi-factor authentication, role-based access control, and integration with Microsoft Entra ID and Okta.

What's included

  • Single sign-on

    SAML and OpenID Connect integrations so users sign in once with their organization's identity provider.

  • Multi-factor authentication

    Phishing-resistant options such as passkeys and security keys, with sensible fallbacks and recovery flows.

  • Role-based access control

    Roles and permissions modeled on real job functions, enforced consistently in the API and the interface.

  • Identity provider integration

    Application registration, claims mapping and group-based access with Microsoft Entra ID and Okta.

  • User provisioning

    Just-in-time provisioning and SCIM-based lifecycle management so joiners, movers and leavers are handled automatically.

  • Access reviews and audit

    Audit logs of sign-ins and permission changes, plus reports that support periodic access reviews.

Specialist areas

Each one has its own page with the detail.

  • Single Sign-On (SSO)

    Let users sign in once with their organization's identity provider, using SAML or OpenID Connect, with clean provisioning and session handling.

  • Multi-Factor Authentication (MFA)

    Add a second proof of identity to sign-in, favoring phishing-resistant passkeys and security keys, with risk-based prompts and safe account recovery.

  • Role-Based Access Control (RBAC)

    Permissions modeled on real job functions and enforced on the server, so every user gets the access their work needs and no more.

  • Microsoft Entra ID (Azure AD) Integration

    Connect your applications to Microsoft Entra ID, formerly Azure AD: app registrations, SSO, group and app role mapping, Conditional Access and provisioning.

  • Okta Integration

    Connect your applications to Okta for single sign-on, MFA, group-based access and automated provisioning, using OIDC, SAML and SCIM.

What problems identity and access management solves

Every application has to answer two questions: who is this user, and what are they allowed to do? When each system answers them separately, users juggle many passwords, former staff keep access longer than they should, and nobody can say with confidence who can see what. Identity and access management (IAM) brings those answers into one consistent model.

We design and build authentication and authorization for custom applications and connect them to the identity provider your organization already runs. Typical goals include:

  • One sign-in for staff and partners through single sign-on, with fewer passwords to reset or leak;
  • Stronger authentication through multi-factor authentication, ideally with phishing-resistant methods;
  • Least privilege through role-based access control, so people get the access their job requires and no more;
  • Clean lifecycle so accounts are created, changed and removed automatically as people join, move or leave.

What a typical engagement looks like

A typical engagement begins with an inventory: user populations (employees, customers, partners), applications, existing identity providers and the current permission sprawl. From that we design a target model covering protocols, token claims, session rules, role definitions and the source of truth for each attribute.

Integration work follows. We register applications in Microsoft Entra ID (the service previously called Azure AD) or Okta, map groups and claims to application roles, and enforce authorization on the server, never only in the user interface. Where provisioning matters, we implement SCIM or just-in-time account creation and make sure deprovisioning actually revokes sessions and tokens.

Rollout is staged. A pilot group moves first, we watch sign-in errors and support requests, and only then do we switch everyone over and retire old password stores.

How to choose between options

Decision Option A Option B
Federation protocol OpenID Connect: modern apps, mobile, APIs SAML: established enterprise and legacy apps
Provisioning Just-in-time: simple, account made at first sign-in SCIM: full lifecycle including deprovisioning
Where roles live Identity provider groups: central control Application database: fine-grained, app-specific rules
Second factor Passkeys or security keys: phishing-resistant Authenticator app codes: broad compatibility

Most organizations end up with a mix: coarse roles from identity provider groups, with fine-grained permissions managed in the application.

Mistakes we design out

Identity projects tend to fail in the same few places, so we check for them deliberately:

  • Authorization only in the interface. Hiding a button is not access control. Every API call checks permissions on the server.
  • Tokens that never expire. We set sensible lifetimes for access and refresh tokens and make sure disabling a user ends their sessions.
  • Role explosion. One role per person defeats the purpose. We keep the role set small and use attributes or scopes for the exceptions.
  • Forgotten service accounts. Machine identities get their own credentials, least-privilege scopes and a rotation plan.
  • Weak recovery. An MFA reset handled by a quick email to support is a back door, so recovery gets the same care as sign-in.

What you get at the end

You get applications that use your organization’s identity provider, an access model that is written down and enforced in code, MFA policies with tested recovery flows, and automated provisioning. Audit logs record sign-ins and permission changes, and a runbook explains how to add new applications and roles without our help.

How we approach it

  1. Map identities and access

    We inventory user types, applications, existing identity providers and the permissions each group actually needs.

  2. Design the target model

    We choose protocols, decide where roles live, and define token contents, session lifetimes and recovery paths.

  3. Integrate and enforce

    We wire up the identity provider, enforce authorization on the server side and remove legacy password stores where possible.

  4. Test the edge cases

    Expired sessions, disabled users, clock skew, role changes and account recovery are tested before rollout.

  5. Roll out in stages

    We migrate pilot groups first, monitor sign-in errors and keep a fallback until the new flow is stable.

Frequently asked questions

Should we use SAML or OpenID Connect?

Use OpenID Connect for new web, mobile and API-based applications, since it is built on OAuth and JSON tokens. Use SAML when an enterprise customer or an existing system requires it. Many applications support both.

Is Azure AD the same as Microsoft Entra ID?

Yes. Microsoft renamed Azure Active Directory to Microsoft Entra ID in 2023. The capabilities and integration protocols remain the same.

Can we add SSO without rewriting our application?

Usually yes. Authentication can often be added at a gateway or through a library in the existing login flow, though authorization checks may need changes inside the application.

What affects the effort of an IAM project?

The number of applications and identity providers, how messy existing roles are, whether you need automated provisioning, and how many legacy accounts must be migrated.

How do you handle users who lose their MFA device?

We design a recovery process up front, such as backup factors or verified help desk resets, because weak recovery undoes the protection MFA provides.

Let's build something great together

Ready to talk about custom software? Tell us about your project requirements and we will get back to you.