Re: Large scale X



Tony wrote:
Russell Shaw wrote:

Hi,
If i have 1000 user accounts on one accounts server and dozens of X apps
on another apps server, how can a user start an X app when they don't have
an account on the apps server? (no user accounts at all on apps server)

(cross-posting removed)

I'm going to break with X tradition, and use the following broad definitions:

1) The server is the machine which has the application we want to run.
2) The client is the desktop PC/X terminal that wants to connect (1) above.

I know that X wants to call the desktop PC the server, and the machine on which the application actually runs the client, but it causes more confusion than it's worth.

My experience with X has been with Linux on a small scale (about 10 users per box), so I'm not an authority. However, I don't think there is any way to run an X application from a server without having an account.

I'm thinking of traditional X where the users use dumb X terminals, and
xdm gives the log-in screen.

The client can use XDMCP to get a list of all available servers on the network, and select a server to connect to. However, a normal system login is still required for a connection.

Do i need to use nfs, or is there some better way?

This depends on your situation. For public access terminals where I work, we setup a single generic account that the general public uses to log into the server. For one of my personal clients, I also have a single account they use with remote X connections. This is a small company where security isn't a big issue.

For cases where security does matter, then yes, you'll need to have accounts on the application server(s) for anyone you want to be able to log in to the machine.

If I understand your question, NFS is neither here nor there.

Hi,
I figured out a way but haven't tried it. The user could log in using the xdm
log-in screen on an X terminal. xdm could be running on the X applications box.
The user can be authenticated by xdm with no user accounts on the apps box, if
pam and LDAP are installed for single-sign-on across the network. Then LDAP
nfs mounts the user account from the accounts box on to the apps box
temporarily for the length of the session.
.



Relevant Pages

  • RE: User Account Migration to New Server
    ... This is Morgan from Microsoft. ... USMT cannot be used to migrate user accounts. ... You can manfully recreate these user accounts on your new server according ...
    (microsoft.public.windows.server.migration)
  • Re: password expiration policy for admin and system accounts ?
    ... Poorly written apps (I guess I cannot say third-party apps in light of ... used as service accounts. ... Microsoft MVP (Windows Server: Security) ... > our old exchange server, the wrong password was specified for an ...
    (microsoft.public.security)
  • Re: password expiration policy for admin and system accounts ?
    ... Poorly written apps (I guess I cannot say third-party apps in light of ... used as service accounts. ... Microsoft MVP (Windows Server: Security) ... > our old exchange server, the wrong password was specified for an ...
    (microsoft.public.win2000.security)
  • Re: SBS Migration, Exchange - help!
    ... so creating all new user accounts is ... The first thing you want is a disk image of the SBS4.5 server. ... first and accounts later, otherwise things break spectacularly. ... Then map a drive to the SBS box that is ...
    (microsoft.public.windows.server.sbs)
  • Re: Deafult email address
    ... > MS is moving away from version-specific groups for server products. ... >> the new addresses to the user accounts. ... > Are you sending out mail directly or forwarding to a smarthost/ISP's SMTP ...
    (microsoft.public.exchange2000.general)