I suppose it's because sunray ebuilds I provided use system gdm provided with
gentoo, which is on your system 64bit. System gdm try to use pam modules from
/opt/SUNWut:
/opt/SUNWkio/lib/pam_kiosk.so
/opt/SUNWut/lib/pam_sunray_amgh.so.1
/opt/SUNWut/lib/sunray_get_user.so.1
which are 32 bit.
So I think you have 2 choices:
1. Compile own 32bit gdm or install 32bit compiled gdm supplied with sunray
software in srss_4.0_linux.zip. In this case you need provide 32bit system
pam modules also.
2. Comment out all sunray pam modules from /etc/pam.d/gdm-srss. In this case
some advanced functionality of sunray software ( amgh, kiosk and
non-smartcard mobility) would not work. But not sure is sunray_get_user.so.1
neeeded. Accourding to post to mailing list from Bob Doolittle
<[EMAIL PROTECTED]>:
"sunray_get_user.so
This module is used by SRSS to acquire the name of the user logging
in in a variety of ways depending on its options:
"prompt" - prompt the user to enter their username
"property=username" - used during redirects and other contexts
where the user name may already be known (e.g. during Non-SmartCard
Mobility login)
"token=<smartcard type>" - used in contexts where 3rd-party
smartcard authentication software may have discovered the username, in
which case the token itself will contain the username (e.g. auth.<username>)"
Anyway I think at first you can try last choice.
On Tuesday 27 May 2008 19:22, Jens Langner wrote:
> Hello Viktar,
>
> today I have read through your new installation guide for installing
> SRSS4.0 on a Gentoo/Linux machine. Here I have an amd64 machine and with
> some more tweaking I was able to get the server base running of SRSS4.0
> with the help of your ebuilds. great!
>
> However, now I am unfortunately stuck where gdm should normally query me
> for the username/password and let me log in. My sunray is already
> showing the gdm login screen of the Gentoo/Linux machine, but right
> before allowing me to enter any password a warning requester
> "Authentication failed" popped up right away. So I am not able to enter
> any username/password in gdm and I doubt that if I would be able to do
> that it would accept that data.
>
> If I run gdm in debugging mode it shows me the following output:
>
> -- cut here --
> ...
> May 27 18:17:02 uranus gdm[14691]: DEBUG: gdm_slave_wait_for_login: end
> verify for ''
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: greeter/SoundOnLoginFailureFile=
> May 27 18:17:02 uranus gdm[14691]: DEBUG: gdm_slave_wait_for_login: No
> login/Bad login
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: greeter/SoundOnLoginFailure=false
> May 27 18:17:02 uranus gdm[14691]: DEBUG: gdm_slave_wait_for_login: In loop
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: daemon/TimedLogin=
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: daemon/TimedLogin=
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Looking up per display value
> for security/PamStack=gdm
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/PamStack=gdm
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/PamStack=gdm
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Requesting group=security
> key=PamStack locale=(null)
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/PamStack=gdm
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/PasswordRequired=false
> May 27 18:17:02 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/RetryDelay=1
> May 27 18:17:03 uranus gdm[14691]: WARNING: Couldn't authenticate user
> May 27 18:17:03 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/UtmpLineAttached=
> May 27 18:17:03 uranus gdm[14691]: DEBUG: Attempting to parse key
> string: security/UtmpPseudoDevice=true
> May 27 18:17:03 uranus gdm[14691]: DEBUG: Display device is /dev/console
> for display :18
> May 27 18:17:03 uranus gdm[14691]: DEBUG: Writing failed session attempt
> utmp-wtmp record
> May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using username
> (unknown)
> May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using type
> USER_PROCESS May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using pid
> 14691 May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using time
> 1211905023 May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using id
> :18 May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using line
> console
> May 27 18:17:03 uranus gdm[14691]: DEBUG: utmp-wtmp: Using hostname
>
> -- cut here --
>
> So my question is, if you have any idea what is going wrong here? I
> highly suppose that this must have something todo with the gdm<>pam
> connection which seems not to work correctly. Looking at the /etc/pam.d/
> directory I can spot the "gdm-srss" definitions you are adding with your
> ebuilds. But are you sure they are correctly used?
>
> So any help is appreciated and if I can get that SRSS4.0 running here on
> Gentoo/Linux I am more than willing to help you with the wiki-page and
> add my own comments to it so that people are able to install it on amd64
> as well.
>
> At least you can already add the "amd64" keyword to your builds because
> all the stuff of your ebuilds compile fine and I just need to manually
> add two links to libldap.so.199 and liblber.so.199 as well as I had to
> install a 32bit version of libsasl2.so.2 to get the utpw command running
> proplery.
>
> As I said, the whole SRSS seems to run fine now, its just the gdm that
> won't let me login for some reason...
>
> Any help is highly appreciated.
>
> jens
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
