Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Planning to Implement
Workspace Domino
Categories Security
Created by Guest
Created on Oct 20, 2023

Support Azure B2C users using OIDC

Given the growing use of Customer identity and access management (CIAM) providers such as Azure B2C, I request an enhancement to Domino to support Azure B2C users using OIDC as it currently supports other relying party Microsoft technologies such as ADFS and Azure Active Directory.

Australia is following other governments such as USA my gov id <-> Azure B2C <-> power apps identity management pattern - see https://github.com/azure-ad-b2c/partner-integrations/tree/master/samples/Login.gov

and Ireland / NZ

https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/azure-ad-b2c-custom-policies-to-build-your-own-identity-journeys/ba-p/382791

Related HCL case is CS0424576

Thanks

  • Attach files
      Drop here to upload
    • Guest
      Reply
      |
      Mar 18, 2025

      Azure B2C "embraces and extends" OIDC in a special and unique way so requires a special workaround.

      Please let us know on the Early Access forums if setting the notes.ini variable OIDC_LOGIN_ENABLE_AZURE_AD_B2C_WORKAROUNDS=1 on a Domino 14.5 Early Access 2 refresh server resolves this problem.