Encrypted password not working for API

Encrypted password for API is no longer supported in v19.0. As API calls are over HTTPS, the password is already secured & encrypted in transit so additional encryption is not necessary. You can continue to use plain password on v19.0. 

Hi Lev Anni I am working with the documentation team to update the "API Help Section" of XG V19  accordingly.

Thank You for that one, too.

BTW: Yesterday I have also tried to read the encrypted password on the Advanced Shell with "opcode GetEncrypted_PasswordFor_API -t json -b '{"password":“<mypassword>"}' -ds nosync" , but I received error "500 opcode not found". It seems this opcode was removed also as pw encryption is not available any longer. So when updating the documentation this might be another passage to take a closer look at.

Greetings

Thank You for that one, too.

BTW: Yesterday I have also tried to read the encrypted password on the Advanced Shell with "opcode GetEncrypted_PasswordFor_API -t json -b '{"password":“<mypassword>"}' -ds nosync" , but I received error "500 opcode not found". It seems this opcode was removed also as pw encryption is not available any longer. So when updating the documentation this might be another passage to take a closer look at.

Greetings