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 Under Consideration
Workspace Traveler
Created by Guest
Created on May 8, 2020

Support Traveler installation on Suse/RHEL server with LDAP user

Traveler installation fails if user and group information is not stored in /etc/passwd /etc/shadow /etc/groups but provided via SSSD (System Security Services Daemon)

Error message is "Error: Invalid username or group specified."

As SSSD is a valid and supported (RedHat, SuSE, ...) way to provide user credentials, please modify Traveler installer to support this way of authentication.

More information on SSSD can be found at https://docs.pagure.org/SSSD.sssd/

  • Attach files
  • Guest
    Reply
    |
    May 25, 2020

    Do you have more details about it? Domino installs and works correctly? You only have an issue with the Traveler install? Both Domino and Traveler use the same installers -- InstallAnywhere and if it is only the installation that makes a difference, it is completly different than having a general run-time issue.

    For Domino to work properly we need defined UID and GIDs. A whois should return a correct user etc. I had issues implementing Domino on Docker with abritary user.id support where I ran into those type of issues.

    I am working with Domino for quite a long time and never came across SSSD.

    But yes it is included in RHEL by default what I just checked.

    IMHO there quirement makes sense -- like supportng SELinux makes sense.

    But providing some more information would be helpful.

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