Login failed for user: test, error: The user does not have a PIN set.Įxception occurred checking agent: SQL Exception: Invalid transaction state. On the Swivel administration console check to see if the setting under Policy/PIN and OTC that the require password for PIN change is set to Yes or No. If using the single Channel TURing image, ensure session request by username is enabled under Server/Single Channel.Ĭhange PIN failed for user: username, error: CHANGE_PIN_PASSWORD_ERROR A correct OTC must be entered before a new OTC is entered. The PIN entered is too simple and breaks the Swivel rules defined in the Administration Console, The default for repeated digits is 0 and allows for no repeated digits. After restarting tomcat if an error persists there might be need to reboot the appliance, see License Key Update.ĬhangePIN failed for user: xxxx, Error: The PIN is not complex enough. A large license may need to be purchased, or users marked a Deleted User may need to be purged, see Delete a Swivel user. Note that this message will be displayed even if a new larger license is installed until Tomcat is restarted. The number of licensed users has been exceeded. The license is invalid or has not been correctly entered.ĮRROR - The number of users in the Pinsafe users group has exceeded the license Also seen in relation to ChangePIN where a user is trying to use the incorrect transport to change their PIN number. In 3.x versions of Swivel it maybe necessary to synchronise with the repository for any changes in these policies to be affected. This error indicates that a user is trying to authenticate against an Agent that they are not authorised to do. Swivel can be configured so that only members of certain groups can authenticate via certain agents. : Error occurred during login for user: xxxxx, error: User does not belong in the correct group within the user repository to continue the authentication attempt : Failed to start a single channel session: AGENT_ERROR_USER_NOT_IN_GROUP. If the user does exist in the repository (eg Active Directory) then Swivel needs to sync with that repository. The requested user does not exist in the database. Session start failed for user: x, error: No Data for user was found. To support this second model Swivel must be configured to Allow Session Start by Username or Allow Image Request by Username. The second way is where those two steps are combined into a single step, an agent just passes Swivel the username, the session is started and the TURing image returned in one step. Firstly an agent starts a session, reads the Session ID and then requests the image by sending the session ID to Swivel. There are two ways that a TURing image can be requested. Session start failed for user: graham, error: Single channel image request by username is disabled. The account should be unlocked by going to the admin console, finding the users account and selecting the unlock option. This error indicates that this session start has failed because the user-account is locked. When a user requests a TURing image or a SMS security string in on-demand mode, this starts a Swivel authentication session. : Failed to start a single channel session: AGENT_ERROR_USER_LOCKED. To identify the root cause retrieve the log files directly from the server. Do not forget to reset the log file size back to a sensible value. If you set the log file size to be very small (eg 10k) and then create a few log entries by requesting TURing images, the log file will roll over to a new file and the log viewer page should again render properly. This is caused by invalid characters in the log file. Check the system logs for errors and see Swivel does not startĬorrupt Log File Stack Trace on Log Viewer screen This can be see when trying to login to the Swivel administration console. Pinsafe is currently not able to run correctly. This page provides more information about these messages, likely root causes and fixes. Additionally, the Swivel logs are stored under /home/swivel/.swivel/logs. Swivel writes information and error messages to its logs files or to a Syslog, which can viewed within the Swivel Admin Console under Log Viewer.
0 Comments
Leave a Reply. |