Skip to main content

Overview

To replace the existing authentication/authorisation architecture (based on Hybris/Spring security) with a composable vendor. This is a key enabler required to perform an iterative migration to a composable architecture

Systems​

  • Auth0 - Authentication & Authorisation 3rd party provider
  • Hybris - Existing MVC website
  • Alderaan / content.rapha.cc - Headless Next.js application.
  • Hybris OCC (Omni Commerce Connect) - API for commerce & data services on the existing version.
  • CommerceLayer - The to-be eCommerce platform that will replace Hybris.
  • Rapha Mobile Application - Our native Android & iOS mobile app for RCC customers.
  • Bloomreach CRM (Exponea) - Uur current CRM platform.

Functional Approach (High Level)​

  • Auth0 will replace existing login, signup, reset password & change email functionality.
  • Auth0 will maintain Rapha’s customer pool from now on, storing a set of core attributes.
    • Related customer data like addresses, will be stored in CRM and ecom platforms.
  • Existing customers from Hybris will be lazy-migrated using Auth0’s capabilities & Hybris OAUTH2.
  • Auth0 will become a custom Authoriser on our AWS API Gateway, so permissions will be handled at Auth0’s level.
  • During the iterative migration from Hybris to CommerceLayer, both systems will co-exist.
  • Hybris will serve pages as-is (MVC website) on the non-migrated areas (PDP, PLP, etc), implementing the autologin-strategy.
  • Hybris will serve a set of data (e.g. wishlist, minicart) & some services (e.g. create customer) via API.
  • CommerceLayer will provide the eCommerce services & data required by the migration via API and/or via their set of hosted applications.
  • CommerceLayer will use SSO and won’t store customers internally.