Identity Architecture

Identity architecture for FoxIDs implementations

FoxIDs helps you turn business requirements, security constraints, applications and existing identity providers into a target architecture that teams can implement and operate.

Talk to an expert All services

Architecture decisions for production

The output is not a detached architecture document. It is a practical FoxIDs design that architects, developers, security teams and operations can use during implementation.

Current-state analysis of applications, APIs, identity providers and authentication methods

Target FoxIDs architecture, federation strategy and protocol choices

Security and compliance considerations built into the design

Current-state analysis

Start with the estate you actually have, not an idealised diagram.

Review existing identity providers, directories, Directory Connector and AD connect options, authentication methods and trust relationships
Map applications, APIs, environments, user groups and claims dependencies
Identify migration risk, compliance constraints and operational dependencies early

Target architecture

Define the FoxIDs model that should guide implementation, migration and future change.

Federation and directory strategy across internal and external identity providers
OpenID Connect, OAuth 2.0, SAML 2.0 and WS-Federation choices by application and environment
Claims, groups, roles and access information designed for applications

Deployment model

Choose how FoxIDs should run, where identity data should be hosted, how the platform should be operated and how separate tenant environments should support development, test, staging and production.

FoxIDs Cloud hosted securely in Europe
Self-hosted FoxIDs in your own environment
Hybrid FoxIDs deployments across cloud and on-premises systems

Identity architecture for FoxIDs implementations

Current-state analysis

Target architecture

Deployment model

Related documentation

Your Privacy