The new native CrypterObject is not supported in PowerServer web. To get around this I've been trying to utilize the bcyrpt and crypt32 dll's in windows with no success however. They always return a null value when I run the app in the web environment (they work fine when the app is run in the standard way). It seems like someone must have dealt with this. Any suggestions? Maybe there is a deployment/configuration step I am missing? I'd like to use the AES algorithm with 128 bit encryption if possible.
Mike, what did you change in the n_bcrypt userobject in order to get things to work in PowerServer? So far I've done the following:
- made sure I'm deploying the 32 bit dll's
- using 'ALIAS FOR' and the ansi encoding option in the external function declarations
- initializing blob variables with Blob('') instead of setnull
Nothing has worked so far. The call to of_hashblob always returns an empty string.
- mike S
- Wednesday, 1 May 2019 16:34 PM UTC
I think that my Cryptoapi code doesn't work because the underlying API requires a user profile. The newer Bcrypt API does not.
I've used HMAC - sha256, as well as the base64 encode/decode from rolands' bcrypt calls:
use the 32 bit version (10.5)
they work in both web and client server
- Thomas Rolseth
- Tuesday, 30 April 2019 14:17 PM UTC
- Page :
However, you are not allowed to reply to this question.