CA ACF2

Expand all | Collapse all

AES256 on CPACF?

Jump to Best Answer
  • 1.  AES256 on CPACF?

    Posted 10-04-2017 07:29 AM

    Hallo community

     

    Ever since we changed our GSO PSWD settings to use AES256 exclusively (PSWDENC=AES2 combined with ONEPWALG) instead of XDES we noticed a significanly higher CPU/service unit usage when a user changes its password as compared to XDES.

     

    Just to give you some figures:

    • Change password for one user, using XDES, several single jobs:
        job 1: 55153 service units
        job 2: 45834 service units
        job 3: 27510 service units
        job 4: 18411 service units
        job 5: 9303 service units
        job 6: 154 service units
    • Change password for one user serveral time in a row, using XDES, one job:
        job 1: 824522 service units
    • Change password for one user, using AES256, several single jobs:
        job 1: 82527 service units
        job 2: 82687 service units
        job 3: 82568 service units
        job 4: 82421 service units
        job 5: 82492 service units
        job 6: 82426 service units
    • Change password for one user serveral time in a row, using AES256, one job:
        job 1: 839169 service units


    Is there a possibility for CA-ACF2 to run the AES256 encryption on CPACF if the hardware is available (should be in every z196, z13, z14 etc.)?



  • 2.  Re: AES256 on CPACF?
    Best Answer

     
    Posted 10-05-2017 11:03 AM

    Since this will require some investigation and research, please open a case in support.ca.com.



  • 3.  Re: AES256 on CPACF?

    Posted 10-10-2017 02:02 AM

    Case 00862632 opened.