Trusted system prblm

[bnkannan]

Hi ,I am kannan .I have got one K class server. When i tried to make the system trusted,ther users whos are all there in the system is not able to logon to the system.It is giving the messages saying that"Account diable please contact accounts administrator and Terminal session disable.What could be the problm.Has anybody knows how the system to made as trusted with proper steps.


Thanks
kannan

[Kofi ARTHIABAH]

More information about trusted systems can be found at:
http://docs.hp.com/hpux/onlinedocs/B2355-90121/B2355-90121.html

but what you describe is not a problem - that is the way it should behave. In order to meet the "trusted" status, certain rules must be met - those rules include such things as passwd length, validity of user accounts... etc. Now if any of your accounts do not meet these criteria, you (the admin) would have to enable them. It is a learning curve for your users (but every security measure should be!)

do a search for trusted system in the forums you will find experiences of others.

[Kofi ARTHIABAH]

More information about trusted systems can be found at:
http://docs.hp.com/hpux/onlinedocs/B2355-90121/B2355-90121.html

but what you describe is not a problem - that is the way it should behave. In order to meet the "trusted" status, certain rules must be met - those rules include such things as passwd length, validity of user accounts... etc. Now if any of your accounts do not meet these criteria, you (the admin) would have to enable them. It is a learning curve for your users (but every security measure should be!)

do a search for trusted system in the forums you will find experiences of others.

(I hope this post is not duplicated...)

[Elizabeth_2]

Hi Kannan!

If a user cannot login after converting to a trusted system,
check the length of the user password from the non-trusted system.
If it was greater than 8 characters, then have them try using only 8
of those characters and see if they can login. The default for
password length for a trusted system is only 8 characters. So only
the first 8 characters will be recognized once trusted (this is
the same for non-trusted, see passwd(1)). If they want passwords
longer than 8, then they will have to increase it using SAM.

I hope this helps!

[Elizabeth_2]

One more thought... you could try:

1. In SAM, under General User Account Policies, disable the
user's security policy referred to as: Maximum Period of
Inactivity on Account (days).

2. Reactivate the account and have the user login.

This will add the u_suclog entry to the user's database file.

3. Enable the user's Maximum Period of Inactivity on Account
(days) security policy.

[Elizabeth_2]

One more thought... you could try:

1. In SAM, under General User Account Policies, disable the
user's security policy referred to as: Maximum Period of
Inactivity on Account (days).

2. Reactivate the account and have the user login.

This will add the u_suclog entry to the user's database file.

3. Enable the user's Maximum Period of Inactivity on Account
(days) security policy.

[Elizabeth_2]

One more thought... you could try:

1. In SAM, under General User Account Policies, disable the
user's security policy referred to as: Maximum Period of
Inactivity on Account (days).

2. Reactivate the account and have the user login.

This will add the u_suclog entry to the user's database file.

3. Enable the user's Maximum Period of Inactivity on Account
(days) security policy.

[Elizabeth_2]

One more thought... you could try:

1. In SAM, under General User Account Policies, disable the
user's security policy referred to as: Maximum Period of
Inactivity on Account (days).

2. Reactivate the account and have the user login.

This will add the u_suclog entry to the user's database file.

3. Enable the user's Maximum Period of Inactivity on Account
(days) security policy.

[Elizabeth_2]

One more thought... you could try:

1. In SAM, under General User Account Policies, disable the
user's security policy referred to as: Maximum Period of
Inactivity on Account (days).

2. Reactivate the account and have the user login.

This will add the u_suclog entry to the user's database file.

3. Enable the user's Maximum Period of Inactivity on Account
(days) security policy.