[CryptoAPI] [CryptoAPI] SaveKey not available anymore?

Forge Component
(19)
Published on 3 Mar by Ricardo Silva
19 votes
Published on 3 Mar by Ricardo Silva

Hi All,


I just updated the CryptoAPI component and noticed that they changed the SaveKey action and the names of a few other actions. Is this a bug or has the methodology to generate and save the key to site properties changed? If so, could we get some guidance of the new process to follow? 

Old:


New:


Solution

Hey André,

I think those screenshots are swapped, the latest version has AES_NewKey, AES_SaveKey, etc.

Have you seen the video at https://www.youtube.com/watch?v=SiyK-JAGpw0 ? It does a nice walkthrough of how to use the latest version to store your data.

Solution

Yes, that was weird, for some reason during updates there was an issue updating that component and seem to have rolled it back somehow, not sure what happened there, reinstalled application, refreshed dependencies all good now.