5 Replies Latest reply: Jul 5, 2012 8:12 PM by Matt Pollicove RSS

3DEScrypt Error

Matt Pollicove
Currently Being Moderated

I have a strange situation going on....

 

I have a workflow that provisions a user in AD using NW IDM 7.2 SP4. The user gets provisioned properly and the password is set.

 

Then I go to change the user's password via Self Service Password reset, the request works through the PF but when it goes to change the password I get: ERROR: Illegal size of buffer when trying to decrypt the password.  This same process (and script) set the password not 5 minutes before.

 

Has anyone seen this before?

 

Thanks,

Matt

  • Re: 3DEScrypt Error
    Ian Daniel
    Currently Being Moderated

    No, sorry! - Not a helpful post, but at least you don't feel ignored!

  • Re: 3DEScrypt Error
    Chris Snyder
    Currently Being Moderated

    Hi,

     

    What encryption function are you using, is it custom or one of the standard ones?   I'm on SP3, but it looks like sap_core_encryptPassword script is using the wrong function in this version.  Would be interesting to see the encryption script you're using.

     

    Note: As of SAP NetWeaver Identity Management Identity Center 7.2, it is recommended to use the function uEncrypt instead

     

    Best Regards,

     

    Chris

    • Re: 3DEScrypt Error
      Matt Pollicove
      Currently Being Moderated

      Hi Chris,

       

      Unfortunately, this is being used for Windows Password reset and uEncrypt does not work in the Windows Engine from what I saw in the HELP.  I'll have to double check the configuration, but I think I used my own script from the previous issues that you had mentioned.

       

      Thanks,

      Matt

  • Re: 3DEScrypt Error
    Ivar Ness
    Currently Being Moderated

    The uEncrypt will use the encryption method set in the keys.ini, hence allowing for the new  3DESCBC.

    The 3DESCBC is stronger than it's predecessor cause same cipher text will look different for each timed

    encrypted. The uDESEncrypt will only use the old version.

    Notably the parameters of uDESEncrypt(key,cipher) are swapped in uEncrypt(cipher,key)  for reason unknown to me.

    I think seen similar error once when the keys.ini file was generated with wrong key lengths.

    if you in the uFunctions use empty value in key field it will get the default key from keys.ini, if you

    have it spesified it use that key value.

    (The same goes for uDecrypt,uDESDecrypt.)

     

    My guess is if these parameters was swapped around you could something like that error message you reported.

Actions