Access management and CIAM
Design authentication journeys, federation, MFA and session rules for each audience.
Access and privileges
Modernise SSO and federation
Simplify access journeys while regaining control over protocols, sessions, applications and responsibilities.
An unreadable SSO is rarely a product problem first. It is a stack of components, protocols and local decisions that nobody holds together any more.
Does this sound familiar?
- Several SSO solutions coexist on top of each other.
- Applications use scattered protocols and configurations.
- Users are asked to reauthenticate far too often.
- Some applications still depend on legacy mechanisms.
- Business teams deploy their own access components.
- Session and MFA rules are inconsistent.
What you are trying to achieve
- Clarify the architecture.
- Rationalise the components.
- Modernise the protocols.
- Improve the user experience.
- Secure sessions and tokens.
- Industrialise application onboarding.
The Ariovis capabilities involved
Each offer keeps its own role. Here is exactly what it brings to this situation.
IAM strategy and Zero Trust
Decide the target, the migration path and the fate of legacy components.
IAM integration
Onboard applications one by one: protocols, attributes, testing, cutover without downtime.
IAM operations
Operate the access platform and absorb the continuous flow of new applications.
Where to start
Map the populations, applications, protocols, identity providers, journeys and migration constraints.
- 01List the identity providers, portals and access components actually in service.
- 02Sort applications by protocol and migration constraint.
- 03Describe the current journeys of the main audiences.
- 04Identify which applications move first and which must be isolated.
See It in Practice
Real engagements whose approach sheds light on this situation.
Sector : Banking
Designing an identity federation strategy
A banking organization wanted to structure its approach to identity federation, related standards and the implementation of Single Sign-On.
Illustrates a comparable approach to designing a federation strategy.
Read the case study : Designing an identity federation strategy
Sector : Banking
Evolving an IAM and Access Management architecture
A banking organization wanted to assess an initial identity architecture designed for a partner use case and define sustainable evolution scenarios.
Shows how to objectively assess an access architecture before changing it.
Read the case study : Evolving an IAM and Access Management architecture
Sector : Non-profit
Rationalizing an IAM landscape around Microsoft
A non-profit organization wanted to rationalize a heterogeneous IAM landscape, simplify operations and build a coherent identity foundation.
Offers useful feedback on rationalising a heterogeneous authentication landscape.
Read the case study : Rationalizing an IAM landscape around Microsoft
Explore the Topic
Our published content that speaks directly to this situation.
Field note
Your business team did not deploy Keycloak to rebuild your SSO
Shows why business teams end up deploying their own authentication stack.
Field note
We are not trying to know everything about a customer
Helps explore the balance between customer journeys and security requirements.
Replay
Balancing security and user experience: preventing fraud through identity
A useful replay on the trade-off between additional controls and journey fluidity.
Understand the Concepts
The notions worth sharing with your teams on this topic.
Does this use case look like yours?
Tell us about your context. Together we identify the priority capabilities and the first useful step.