Password Safe and Repository

Login problems

Login problems

Previous topic Next topic  

Login problems

Previous topic Next topic  

If a problem should arise at the login, you can find notes about the reason and the solution in this chapter.

 

Problem:
Reason:
Solution:

Error at the user authentication. Please make sure that you log in with domain/user. Client error.
Client could not carry out the login. Usually the password is wrong here.
Make sure that the right password is used, that the shift key is not activated and that keyboard language is not altered.



Problem:
Reason:
Solution:

Error at the user authentication. Please make sure that you log in with domain/user. Server error
Server could not carry out the login. Usually the password is wrong here.
Make sure that the right password is used, that the shift key is not activated and that keyboard language is not altered.



Problem:
Reason:
Solution:

No authorization for the user authentication.
User must not be used for the AD login, because he/she does not comply with the user logged in at the operating system.
Log off at the operating system with the right user. Alternatively the option can be deactivated in the user settings.



Problem:
Reason:
Solution:

Logged in Windows user cannot be used for the user authentication.
The login cannot be carried out because the user logged in at the operating system does not comply with the user that wants to log in at Password Safe.
Log off at the operating system with the right user. Alternatively the option can be deactivated in the user settings.



Problem:
Reason:
Solution:

No authorization for the automatic user authentication.
The user does not have enough rights for the automatic login.
Make sure that the user has got the appropriate rights.



Problem:
Reason:
Solution:

The configuration of the user authentication is not correct. Therefore the auto login cannot be carried out.
Automatic login with an Active Directory user failed, because the Public Key is not correct.
Try to configure the automatic login again.



Problem:
Reason:
Solution:

Error at the user authentication. Client locked.
The user that should be logged in could not be found, therefore the IP address of the accordant client has been locked.
Make sure that the user name is spelled properly and that the user is installed in Password Safe.        



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login because the signature has not been confirmed.
Error at checking the signature.
Check if the client and the server have got the same version.



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login because it is not trusted.
Server does not trust the certificate.
Check the certificate.



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login because it is expired.
The certificate is expired.
Renew the certificate.



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login because the fingerprint does not comply.
Server could not confirm fingerprint.
Check the certificate and issue it again if necessary.



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login, because the CA cannot be reached.
The necessary certificate authority cannot be reached.
Check the connection with the accordant server.        



Problem:
Reason:
Solution:

The used certificate cannot be used for the user login because no user has been found for it.
User from the certificate has not been found in Password Safe.
Make sure that the user in Password Safe has got the same name as the user in the certificate.



Problem:
Reason:
Solution:

The user found for the certificate is not logged in at the system. Login at Password Safe is not possible.
The login cannot be carried out because the user logged in at the operating system does not comply with the user that wants to log in at Password Safe.
Log off at the operating system with the right user. Alternatively the option can be deactivated in the user settings.