[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Help! Redhat 7.2 GUI login as OpenLDAP client

Do not know if anyone has such a problem before and have had a better 
solution, but I, encouraged by Ingo, would like to post a trial method 
to resolve the Gnome login issue with LDAP clients 

>From Ingo's hints I managed to make the linux clients to work.

Since I did not change any gnome setting during my ldap client set up, it 
seems there is no problem with the gnome login at all. However the 
redhat's "authconfig" process did not configure the gnome ever and it 
only configures the authentication mechanism. 

As long as your use gnome login interface to try login your ldap account,
you need to have a homedirectory in the local machine. In that home 
directory you should have .gnome, .Xauth* or maybe otehr .* files included.  
you may also need to change the ownership as well.

I am wandering if redhat has a solution to that issue. Do we need to 
manually do that to make gnome login to work? Is there a way to do it 

Unlike solairs the default shell for Redhat user is bash and you may need to 
resolve the shell setting conflict in the passwd.ldif for ldap server. 

Jihua Zhong
Law School of UPENN
Philadephia, PA 19104

> Am Mit, 2003-01-22 um 17.27 schrieb JIHUA ZHONG:
> >  I believe my authentication set up is all right.
> It seems so.
> > However when I used the 'failsafe' session as GUI login session I can 
> > login by using any ldap account and passwd. but that is not what I want 
> So the login-stuff is working and something other not.
> > and I want to use gnome login since there is better desktop interface. 
> Maybe some problem with the gnome session setup?
> In RH8 is something called gconfd, which keeps your settings like window
> focus policy, colors, desktop icons, running programs and so on.
> I don't know, how it is in RH7.2
> But there must be sth, which takes care of these things. If you have
> local users, their settings are usually saved in their home-drive.
> If you log in with an account, whose home-drive does not exist, how
> should the setting be loaded?
> Failsafe works, because the defaults are used.
> Just my explanation
> Ingo Schaefer