OktaAutodistribution2021 → 2026
Secure access for 23,000 users with Okta
Background security work: find the email of every user in every garage, create their access in Okta, and move from a shared alphanumeric login to email sign-in. One identity for Autossimo V3 and V4, the back office, the returns app and the APIs.
- Identity
- Security
- Okta
- Data quality
Impact
- 23,000+users on a single identity
- 1login system for Autossimo, the back office, APIs and SSO
- An alphanumeric login, sometimes shared by a whole garage
- Duplicates, inactive accounts, unknown emails
- No way to know who did what
- One identity per person, with their email
- Okta groups per application and per API
- One sign-in for Autossimo V3 and V4, the back office, returns and the APIs
Users are managed individually, with permissions per person. New services, like the Returns platform, plug into the same identity.
Metrics trackedActivation rateLogin failuresAccess tickets
The engagement Autossimo, Autodistribution's B2B e-commerce platform: 23,000 automotive professionals, 3 million catalogue parts, €700M in annual business, several interconnected management systems (ERPs). Freelance Senior Product Owner from January 2021 to October 2026, with business teams, IT, the integrator SQLI and partners.
The brief
Give every user a personal identity in Okta, with their email, and drive Okta's integration and rollout on the back office and on Autossimo V3 and V4.
The context
Before, everyone signed in the old way: a login, sometimes just an alphanumeric code, and a password. One access could be shared by a whole garage: no way to know who did what, handle someone leaving, reset a password cleanly or grant the right permissions. Moving to email first meant knowing everyone's email, while the database held duplicates, inactive accounts and several kinds of access.
The challenge
Not a project like the others: background work, carried out garage by garage. Get the email of every user in every garage, create their access without locking anyone out because of an old account, and align Okta groups with applications: being in Okta does not automatically grant the right permissions.
What I did
Inventory users and collect their emails
Identify every user of every garage behind the old logins, get each one's email, and agree with SQLI and the identity teams on how to handle duplicates and inactive accounts.
- Data quality
- SQLI
Define the identity model and groups
One person, one account, email as the identifier, several users per garage. Okta groups that open each application: Autossimo, the back office, the returns app, and dedicated groups to authorise calls to each API.
- Okta
- Access groups
Create access in Okta
Identities and groups created in Okta, with changes propagated automatically from the back office: permissions stay current with every new user or departure.
- RabbitMQ
- Back office
Integrate Okta with the back office and Autossimo V3 and V4
Drove Okta's integration as the shared sign-in system: back office, Autossimo V3 and V4, APIs (OAuth2, OpenID Connect) and single sign-on (SSO) to new services such as the returns platform. Email activation, password recovery and password change journeys.
- OAuth2
- OpenID Connect
- SSO
Roll out email sign-in
Moved 23,000+ users from alphanumeric login to email and password. Testing of access, permissions, recovery and sign-out, with garages supported through the transition.
- 23,000+ users
- Acceptance testing
Unify groups in production
Access groups unified in production in October 2026, with scope checks and a rollback plan: a clean-up done with no loss of access.
- Rollback plan
My role on this project
Background security work, driven all the way to rollout.
- InventoryEvery user of every garage, and their old identifiers.
- CollectEach user's email, with duplicates and inactive accounts handled.
- ModelOne person, one account; Okta groups per application and per API.
- CreateIdentities and groups in Okta, kept up to date from the back office.
- IntegrateOkta plugged into the back office, Autossimo V3 and V4, returns, the APIs.
- Roll outFrom alphanumeric login to email: activation, support for garages.
- RunGroups unified in production, permissions tracked, access tickets handled.
Testing, properly tooled Acceptance test suite restructured in Qase, test cases generated and automated with AI, every fix retested and every incident turned into a regression test.

