#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

Allow SAML and ADFS to use other field besides the Email Adress for mapping

Not all users in an AD is assigned a unique  e-mail address, some share the same mailbox with others. Nearly always these AD user accounts have a unique username that could be used instead for the mapping of the AD user to the corresponding user account in the Domino directory and thus allowing them the proper validation and access to the Domino application.

  • Guest
  • Jan 22 2019
  • Assessment
  • Attach files
  • Guest commented
    8 Aug 03:56am

    This limitation cripples Domino's SAML support.

  • Guest commented
    25 May 03:16pm

    Now - after 3 years - any updates on this. We really need to be able to read additional attributes from the SAML assertion. Alternatively store the entire SAML assertion in as a Notes document. PasswordPower from PistolStar could do this 10 years ago.

  • Guest commented
    18 Nov, 2021 03:13pm

    Yes, please. I have a customer requesting this right now

  • Guest commented
    7 Sep, 2020 11:50pm

    The O365 SAML implementation allows for an additional 5 parameters to be passed as "assertions" in the SAML logon... Domino completely ignores these assertions but if Domino could pass them as valid parameters associated with the authenticating user, these additional paratements chould be used to map to ACL's on Domino, thus allowing for Domino security to be supported with AAD logins

  • Guest commented
    22 Jan, 2019 09:31pm

    Absolutely! Yes please! I have customers who are using other names already.
    I have a customer with an unique company ID.
    The IdP is using LDAP and that attribute is their primary name there as well.

    The mapping worked because that entry is unique and in the fullname field of the user.
    But it's unsupported!

    Using that attribute was the only common name in all directories and it would have been a show-stopper.

    I have multiple customers with this requirement. And I don't see why it should be complicated to support it when the name is in the fullname field or any other field that is in the same namelookup.


    [ Daniel Nashed / http://blog.nashcom.de ]