UPMLOGIN

configuration scenarios


Contents

zurück
Scenario 1: UPM used for TNLOGIN only
Scenario 2: allow telnet login for admins only
Scenario 3: allow telnet login for certain users only
Scenario 4: allow telnet login for members of certain users groups only
Scenario 5: let (some/all) userid/password combinations be verified against a LAN/WARP Server domain
Scenario 6: let only some userid/password combinations be verified locally
Scenario 7: let TNLOGIN display some debug output during login


Scenario 1: UPM used for TNLOGIN only

Situation: You have not used your local UPM yet.

What you want: You just want to allow some certain users to login via telnet.

What you do: Just configure those users and their passwords within your local UPM.
[Top]

Scenario 2: allow telnet login for admins only

Situation: You have already some users configured within your local UPM.

What you want: You feel, that only local administrators (like you) should be able to login via telnet.

What you do: Create a user named TNUSER in the local UPM and make this user an administrator. This tells TNLOGIN to allow only administrators to login.

Note:


[Top]

Scenario 3: allow telnet login for certain users only

Situation: You have already some users configured within your local UPM. You do not use UPM groups yet.

What you want: You want only some of the users, that are already defined within your local UPM, be able to login via telnet.

What you do: Create a user group TNLOGIN within the local UPM and make the users, that you want to allow telnet login, members of that group

Note:

  • For users, that are only defined in the LAN/WARP Server domain, you need to create local dummy accounts within your local UPM, so that you can make them member of a local group. You can create inactive accounts without a password for that purpose.

[Top]

Scenario 4: allow telnet login for members of certain users groups only

Situation: You have already some users configured within your local UPM. Those users are already members of self-defined user groups.

What you want: You want only some of the users, that are members of those certain user groups, be able to login via telnet, but you don't want to make use of the TNLOGIN group, because that increases your administrator work.

What you do: Delete the TNLOGIN user group (if it exists), create the TNUSER account and make the TNUSER account a member of all those groups, which member you want to allow telnet login. In order to be able to login, a user must be member of at least one of the groups, that TNUSER is a member of.

Note:

  • For users, that are only defined in the LAN/WARP Server domain, you need to create local dummy accounts within your local UPM, so that you can make them member of a local group. You can create inactive accounts without a password for that purpose.

[Top]

Scenario 5: let (some/all) userid/password combinations be verified against a LAN/WARP Server domain

Situation: You want to enable some users to login via telnet, which are also defined in the default LAN/WARP Server domain of your workstation.

What you want: You want to enable those users to login via telnet, but they should be able to use the same password as the use for LAN/WARP Server logon.

What you do: Create the special group TNLOGIN_VERIFYDOMAIN and

  • make either TNUSER member of that group in order to let all userid/password combinations be verified against the domain.
  • make only certain users member of that group in order to let only userid/password combinations of those users be verified against the default domain of your workstation.

    Note:

    • you need to create local dummy accounts for those users within your local UPM, so that you can make them member of a local group. You can create inactive accounts without a password for that purpose.

[Top]

Scenario 6: let only some userid/password combinations be verified locally

Situation: You have configured to verify all userid/password combinations against the default LAN/WARP Server domain of your workstation.

What you want: Now you want to allow a new user to login via telnet, that has no account in that domain.

What you do: Create the special group TNLOGIN_VERIFYLOCAL and make that new user a member of that group.
[Top]

Scenario 7: let TNLOGIN display some debug output during login

Situation: One of your telnet users cannot login via telnet and you have no clue, what the error is.

What you want: You want TNLOGIN to display some debug information durin login, so that you can determine the error reason.

What you do: Create the special group TNLOGIN_DEBUG and

Note:

  • The additional debug output is only available in english.
  • When debug output is activated, TNLOGIN waits for a keystroke, after a login error occurred.

[Top]


Impressum Search This website in other languages Last update: 15. Jul 2008 © Christian Langanke 1997-2012