Purpose
This page handle fatal errors while trying to Login, for example:
For more information, refer to: Login
CAST AIP Versions
AIP Version | Yes/No |
---|---|
8.3.x |
Applicable Platform or <Sub Platform Version>
Imaging version | Yes/No |
---|---|
2.x |
Observed on RDBMS
RDBMS | Yes/No |
---|---|
CSS |
Action Plan
Depending on user authentication methods for CAST Imaging System check if the configuration was correctly managed -Configure authentication. From example in LDAP mode, many users encountered this error because of wrong DN, missing port... as an example of LDAP configuration, you should get something like the following:
security.ldap.url=ldap://*****.****.****.com/ security.ldap.account.dn=CN=Amine Benarbia,OU=USERS,OU=FR,DC=****,DC=*******,DC=**** security.ldap.account.password=**** security.ldap.usersearch.base=DC=****,DC=********,DC=**** security.ldap.usersearch.filter=(&(objectClass=user)(sAMAccountName={0})) security.ldap.groupsearch.base=DC=****,DC=********,DC=**** security.ldap.groupsearch.filter=(&(objectClass=group)(member={0})) security.ldap.groupsearch.base.filter=(&(objectClass=group)(member={0}))
- If you are running Imaging on a version below 2.5.0 and if you are switching from a user authentication method to another then take into account the following points:
- Whenever you switch to a new authentication mode, i.e. from local to Active Directory, or vice-versa, you must run a batch file to clean up any roles that have been assigned to users in the previous authentication mode, For more information refer to Clean up when switching to a new authentication mode
- When switching from SAML mode back to any other mode, do not forget to reverse the changes you made to the CAST Imaging System login service to force it to use the HTTPS protocol, For more information refer to Clean up when switching to a new authentication mode
If the steps above do not help to solve the issue then contact CAST Technical Support with the following Relevant Input
Notes/comments
Related Pages