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:
-
You can create an inactive TNUSER account without a password for that purpose.
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.
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.
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.