headers
Joseph Acquisto | 5 Jun 2012 15:53
Favicon

OES11 KDE login fails for LUM users

Fresh OES11 install.   There was an error during install "sysadmin failed creating the directory objects". 
But only that.  Several hits on that, but nothing seems pertinent.

The only issue (so far) is that LUM users cannot login.   Did find lum users group was not included in groups for
the server.  Added that.

In a terminal session, as root, "id lum_users" reports user is seen and belongs the the expected groups.

When attempting a login via KDE GUI, /var/log/messages shows"
------------------------------------------------------
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: pam_sm_authenticate in pam_ncl.c (novell-client's
pam)is called 
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: inside ncl pam : user name obntained is : [_My-User]
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: Password is already available to the NCL PAM module. So
reprompting for password
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: pam_ncl.c:pam_sm_open_session called
Jun  5 09:33:51 my_server pam_autoncl[7253]: pam_ncl_autologin authenticate started.
Jun  5 09:33:51 my_server pam_autoncl[7253]: Single Sign On Getting User FDN starts here ...
Jun  5 09:33:51 my_server pam_autoncl[7253]: dlsym failed...failed 
------------------------------------------------------

When attempting a text login (putty) log shows:
------------------------------------------------------
sshd [11915]: error: PAM: Authentication failure for LUM_USER from  somenumbers <at> mydomain.mytld
-----------------------------------------------------

Can't find any thing for the dlsym failed message.  I don't recognize the host name in the sshd failure, but
will try to track it down. 

Hoping there may be some info from the trenches on this.
(Continue reading)

Permalink | Reply |
headers
Joseph Acquisto | 5 Jun 2012 16:04
Favicon

Re: OES11 KDE login fails for LUM users

The "unknown" is simply my own PC, from which I was logging in.  Time for a wakeup cup.

joe a.

>>> "Joseph Acquisto" <joea <at> j4computers.com> 06/05/12 9:56 AM >>>
Fresh OES11 install.   There was an error during install "sysadmin failed creating the directory objects". 
But only that.  Several hits on that, but nothing seems pertinent.

The only issue (so far) is that LUM users cannot login.   Did find lum users group was not included in groups for
the server.  Added that.

In a terminal session, as root, "id lum_users" reports user is seen and belongs the the expected groups.

When attempting a login via KDE GUI, /var/log/messages shows"
------------------------------------------------------
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: pam_sm_authenticate in pam_ncl.c (novell-client's
pam)is called 
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: inside ncl pam : user name obntained is : [_My-User]
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: Password is already available to the NCL PAM module. So
reprompting for password
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: pam_ncl.c:pam_sm_open_session called
Jun  5 09:33:51 my_server pam_autoncl[7253]: pam_ncl_autologin authenticate started.
Jun  5 09:33:51 my_server pam_autoncl[7253]: Single Sign On Getting User FDN starts here ...
Jun  5 09:33:51 my_server pam_autoncl[7253]: dlsym failed...failed 
------------------------------------------------------

When attempting a text login (putty) log shows:
------------------------------------------------------
sshd [11915]: error: PAM: Authentication failure for LUM_USER from  somenumbers <at> mydomain.mytld
-----------------------------------------------------
(Continue reading)

Permalink | Reply |
headers
Joseph Acquisto | 6 Jun 2012 17:03
Favicon

Re: OES11 KDE login fails for LUM users

FWIW -

It was a PAM thing.

After finding info that called out a differently named module, and not finding that file, tried "yast2
novell-lum".   Oddly not available from "yast2" alone.

And, sure enough, a config utility came up.   However, xdm was not amongst the items that could be selected.  
Hmm.  Checked those I might use and saved the changes.

Checked to see what it modified in /etc/pam.d.   xdm was not one of them.  Backed that up and copied sshd to xdm,
having checked that I could log in using ssh from another unit.   

KDE login now works fine.

>>> "Joseph Acquisto" <joea <at> j4computers.com> 06/05/12 9:56 AM >>>
Fresh OES11 install.   There was an error during install "sysadmin failed creating the directory objects". 
But only that.  Several hits on that, but nothing seems pertinent.

The only issue (so far) is that LUM users cannot login.   Did find lum users group was not included in groups for
the server.  Added that.

In a terminal session, as root, "id lum_users" reports user is seen and belongs the the expected groups.

When attempting a login via KDE GUI, /var/log/messages shows"
------------------------------------------------------
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: pam_sm_authenticate in pam_ncl.c (novell-client's
pam)is called 
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: inside ncl pam : user name obntained is : [_My-User]
Jun  5 09:33:51 my_server kdm: localhost:2[7253]: Password is already available to the NCL PAM module. So
(Continue reading)

Permalink | Reply |
headers
jrd | 6 Jun 2012 17:07
Picon
Picon
Favicon

Re: OES11 KDE login fails for LUM users

	For OES11, when installing the products go into LUM configuration and 
select the services to be LUM enabled. gdm (the GUI, whether KDE or 
Gnome) is one of them. Change OES components through the OES 
configuration portion of YaST as they are coupled in mysterious ways.
	Joe D.

On 06/06/2012 16:03, Joseph Acquisto wrote:
> FWIW -
>
> It was a PAM thing.
>
> After finding info that called out a differently named module, and not finding that file, tried "yast2
novell-lum".   Oddly not available from "yast2" alone.
>
> And, sure enough, a config utility came up.   However, xdm was not amongst the items that could be selected.  
Hmm.  Checked those I might use and saved the changes.
>
> Checked to see what it modified in /etc/pam.d.   xdm was not one of them.  Backed that up and copied sshd to xdm,
having checked that I could log in using ssh from another unit.
>
> KDE login now works fine.
>
>
>>>> "Joseph Acquisto"<joea <at> j4computers.com>  06/05/12 9:56 AM>>>
> Fresh OES11 install.   There was an error during install "sysadmin failed creating the directory
objects".  But only that.  Several hits on that, but nothing seems pertinent.
>
> The only issue (so far) is that LUM users cannot login.   Did find lum users group was not included in groups
for the server.  Added that.
>
(Continue reading)

Permalink | Reply |

Gmane