nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue logging into TeamSite via LDAP when local Unix account exists

System

We have configured our TeamSite development server to allow authentication of users via their LDAP accounts, by adding a section to our /.software/TeamSite/conf/roles/user_databases.xml file.

As a result, I am able to successfully log onto TeamSite ContentCenter using LDAP username 'mannsimo'. However, if a local Unix account is created on the TeamSite server, with the same username, I am then unable to log into TeamSite ContentCenter via my web browser. The LDAP user disappears from TeamSite.

Is there a reason for this and is there a configuration change which can be made, to enable both local and LDAP accounts with the same username to co-exist, without causing conflict?.

I need a local Unix account so I can connect to the server via PuTTY and run commands and edit config files.

Find more posts tagged with

Comments

Crsb

yep that is the known behavior when both accounts (ldap and OS) have the exact username 'mannsimo', you will have to just stick to the OS account if you want ssh access or you could create 'mannsimo2' for OS access.

Migrateduser

Why do you need both a local and LDAP account? That makes no sense. You cannot have the same user as an LDAP user and an OS user. Use PAM for configuring your OS users so they can log in with their network passwords.

windy

We have configured our TeamSite development server to allow authentication of users via their LDAP accounts, by adding a section to our /.software/TeamSite/conf/roles/user_databases.xml file.

As a result, I am able to successfully log onto TeamSite ContentCenter using LDAP username 'mannsimo'. However, if a local Unix account is created on the TeamSite server, with the same username, I am then unable to log into TeamSite ContentCenter via my web browser. The LDAP user disappears from TeamSite.

Is there a reason for this and is there a configuration change which can be made, to enable both local and LDAP accounts with the same username to co-exist, without causing conflict?.

I need a local Unix account so I can connect to the server via PuTTY and run commands and edit config files.

I have the same setup as you. I can login to TeamSite with my Ad credentials and I can putty to the TeamSite server with my OS account. If the LDAP option disappears from the Manage users area, it looks like you LDAP configuration is not quite right.

Migrateduser

I have the same setup as you. I can login to TeamSite with my Ad credentials and I can putty to the TeamSite server with my OS account. If the LDAP option disappears from the Manage users area, it looks like you LDAP configuration is not quite right.

Did you even read the OP? They tried to set themselves up as both a TeamSite LDAP user AND a TeamSite OS user. Pay attention.

Migrateduser

When you say "Use PAM for configuring your OS users so they can log in with their network passwords", do you mean use the authenticate_by=pam mode to allow users to use their LDAP credentials to log onto either TeamSite ContentCenter or via SSH using PuTTY?.

I know our IT team will not allow us to integrate SSH access with Active Directory, so I am thinking we may just have to use local Unix user accounts, such as 'mannsimo2' in order to run local commands etc.

Migrateduser

Yes I think so. I'm not sure how it works with Putty - the Unix folks here set us up with OS accounts. I have a feeling they are separate - meaning the Unix shell login has nothing to do with PAM, although I could be mistaken. Meaning I'm not sure how TeamSite could be used to control Unix Shell access. I do know that TeamSite users set up as OS users use PAM to be able to login using their network (LDAP) authentication.