"Neal A. Lucier" <[EMAIL PROTECTED]> wrote: > ... > I have heard second hand that login fails after the username has > been entered in NSCM dtlogin window. The window to enter a > password never appears. > > What are these "mobile.username" sessions, and if they are errors > is there an automated, sensible way to fix them?
The mobile.<user> token is associated with the session that presents the authentication dialogue during an NSCM login. It's a synthetic internal token, really just a quirk of the current NSCM implementation. A mobile.* session should live for only as long as it takes the user to authenticate to NSCM; this typically calls for the entry of a password but the interaction is driven by PAM so in principle other activities could be required. If mobile.* sessions are living for an extended span of time then something is wrong. (I'm discounting the possibility that people are just getting as far as the authentication challenge and then walking away from the Sun Ray, that would be strange. And I think that even in that case I think the dialogue would eventually time out, although I'm not certain on that.) This doesn't sound familiar. I'd start by making sure that I was current with SRSS patches. If you're already current then I'd open a support call, this isn't something that you're likely to be able to diagnose or fix on your own. OttoM. __ ottomeister Disclaimer: these are my opinions. I do not speak for my employer. -- ___________________________________________________ Play 100s of games for FREE! http://games.mail.com/ _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
