XUA: XYGATEUA Process Abends Multiple Times with Various Stack Traces

XUA: XYGATEUA Process Abends Multiple Times with Various Stack Traces

When the user attempts to change the password to a value that doesn't meet the Safeguard complexity requirements, SAFEGUARD returns a message longer than the space that has been allocated in the XUA, and the XUA program abends.

The workaround is:
     SAFECOM ALTER SAFEGUARD, PASSWORD-ERROR-DETAIL OFF
This would cause this error message instead of saveabend: Password supplied does not meet the minimum complexity requirements, access denied

If you are unable to locate the solution needed or need additional assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XUA: Does XUA support multiple RADIUS servers

      XYGATE User Authentication (XUA) Version 2.25 and later can be configured to support multiple Radius servers by specifying each server name next to the RADIUS_HOST keyword in the UACONF file, using a comma-separated list of server names with no ...

    • XMA: XUA Mover abends when processing XUA protocol types

      Solution: Upgrade to XMA 2.45 or other Cause: XMA 2.43 and older could not properly extract protocol from XUA audits The issue is addressed in XMA Version 2.45 * ITID 245-13395 Update to Extract protocol type from XYGATE User Authentication (XUA) ...

    • XUA: Radius with MSCHAPv2 Not working with Multiple Hosts configured

      As of XUA 2.40 the Radius_Host parameter in the UACONF does not support multiple hosts when using MSCHAPv2 as the Radius Authentication Method. This does work properly with a single Radius host configured. If you are unable to locate the solution ...

    • XUA: How to do an XUA monitor

      1. Uncomment the MONITOR keyword in the UACONF file by editing the file and removing the ?!? from the first position in the line. The modified line should look as follows: MONITOR $S.#XUA.MONITOR Note: If your spooler does not have a collector called ...

    • XUA: No XUA audit records have been found since an FSE 43 occurred.

      After resolving the FSE 43, the XUA SEEP ($XUA) must be bounced to start auditing. Example: $SYSTEM XYGATEUA 4> XUA_SAFECOM_BOUNCE