#dominoforever | Product 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

SSO with multiple Connections/Domino instances

We are hosting Connections for multiple cusomers - each with its own Websphere realm. HCL does not support anymore multi-tenant for Connections starting with 8.0.

Our goal is to use a common kubernetes environment hosting Sametime Premium for those multiple customers with multiple realms. That means we need to enable multiple Ltpa tokens as well as multiple SAML IDP urls, one for each customer. Best will be also hosting multiple meeting urls like

  • customerA.example.com

  • customerB.example.com

in one k8s environment and use for each a separate Ltpa token and SAML url.

  • Guest
  • Jan 20 2023
  • Needs Review
  • Attach files
  • Guest commented
    21 Jan 12:19pm

    Also you would need some technique to limit what email addresses that comes from one saml connection. Otherwise your solution could get malicious calls.

    If one of your connections would like to access another one then can just switch emailsadress on a AD account and get someone else access.