We installed the LINE v2 package on our staging instance, configured a LINE service, a LINE v2 external account, both LINE workflows are running with schedulers (deleteBlockedLineUsersV2 & updateLineV2AccessToken --> it gives us an "update token" so the login/authentication/connectivity works well) and a Line V2 delivery.
The option NmsLine_AESKey is configured and uses a value generated by a JS in workflow: "var x = execCommand('openssl rand -base64 32'); logInfo(x);"
The delivery is executing well, as expected, but the generated broadLogs fail with error "Error in delivery part XXX: invalid AES decryption string"
Any idea? Thanks
Still investigating, the delivery makes a call to:
> lineConnector-v2.js and function :
>> processDeliveryPart (deliveryPart) calls:
>>> LineAppV2.decryptLineUserId(NL.XTK.toString(msg.@address), aesKey) calls
>>>> decryptString(str, key, false); @throws (new StringGroup("nms:line")).decryptError()
which ACC version are you using?
Can you check following:
Normally the encrypted user ID should start with a @ sign in current version, so the ID shown in your screenshot looks weird.
Thanks for your reply
We're using ACC v6 build 8857. Which version are you using? Did you encounter the same error?
ok, Campaign expects that the address in the deliveryLog contains the encrypted Line ID and then tries to decrypt it.
That's the place where it fails for you.
You should crypt the ID Ud7* with the NmsLine_AESKey before sending a message.
Thanks a lot, we could encrypt/decrypt the user id using LineAppV2.cryptLineUserId(lineId, aesKey) and decryotLineUserId in JS successfully.
However, it appears that the connector is not using the right lineUserId, it somehow displays #NAME#
broadlog with #NAME#:
Modified connector in order to debug:
So for an unknown reason, ACC tries to decrypt the string "*" instead of the encrypted line id "@Np620N9hcd..."
Thank you very much
I'll dig more in this subjet early 2020, no news at the moment
Let me know if you find anything useful!
Edit: glad to know you have the same issue, at least it's not an individual problem