XPQ: Running the PASSWORD program in a mixed-release XPQ Environment

XPQ: Running the PASSWORD program in a mixed-release XPQ Environment

In a NonStop network where some systems are running XPQ 3.35 and later and others are running pre-XPQ 3.35 versions, password changes should be initiated from the systems running XPQ 3.35 and later versions so that the password change will be propagated to all systems.

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



    • Related Articles

    • XUA/XPQ: Using Password Program to change passwords for RSA or Radius users

      If executing the HPE password program or an XPQ version of PASSWORD prior to the XPQ release 3.45, then a UAGROUP(s) must be added to the UAACL file (XUA) to process the authentication when the requestor is the PASSWORD program and the user is a user ...
    • XPQ: Workaround for INCORRECT OLD PASSWORD message (XPQ 3.40 and earlier versions)

      Add a UAGROUP to the top of the UAACL file similar to the following: UAGROUP PASSWORD-CHANGES-FOR-RSA-USERS DESCRIPTION "PASSWORD changes for RSA users using the XPQ PASSWORD program" FROM_USER $EVERYONE TO_USER $RSA-USERS REQUESTOR ...
    • XPQ: Password Quality(P15) 3.33 release notes.

      The complete SOFTDOC file for this release is available on the XYPRO website, https://www02.xypro.com/xypro/members/download_release/detail/P15. The updated Reference Manual is available on the XYPRO website, ...
    • XPQ: How to implement split password.

      Example of a PQGROUP entry for the PQACL file: ! Split password creation ! PQGROUP SPLIT_PASSWORD_EXAMPLE ACL $AUTHORIZED OWNER $SECURITY MEMBERS $SENSITIVE PASSWORD_EXPIRE off SPLIT 2 The customer needs to run the password command as a member of the ...
    • XPQ: dh1024 encryption is ignored for XPQ version 3.20 and greater.

      Q. The softdoc for 3.20 says it will "ignore" "dh1024" part of "des168,dh1024". Encryption is still done using the algo in the first argument. What was changed was the key generation method, the key is generated internally now, so the "dh1024" is ...