Skip to main content
Level 4
Jun 12, 2019 2:11 PM UTC

LINE v2 delivery error with AES key: invalid AES decryption string

Hi,

Has someone ever succeeded to install the LINE v2 standard package, in order to send LINE messages (marketing doc: LINE : Free Calls & Messages  and dev doc: LINE Developers )?

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

PS:

External account:

Line account:

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

8 replies

Level 4
Jun 12, 2019 3:55 PM UTC

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()

Translate
Adobe Employee
Jun 20, 2019 5:29 AM UTC

Hi,

which ACC version are you using?

Can you check following:

  • Verbose logs when a new follower is added
  • ID stored after following, can you decrypt that with a decrypt string call in JS?

Normally the encrypted user ID should start with a @ sign in current version, so the ID shown in your screenshot looks weird.

Translate
Level 4
Jun 20, 2019 8:27 AM UTC

Hi Ramon,

Thanks for your reply

We're using ACC v6 build 8857. Which version are you using? Did you encounter the same error?

  • What logs? At the moment, when a new follower subscribes to our Line profile, it doesn't get added to our Recipients database. I set up a simple jssp (https://my.custom.domain.com/my_nms/test-line-webhook-event.jssp) and I used it in the Line setting "Webhook URL", but I'm not sure this step is needed. And when I hit Verify, it says "Success"
  • The id used in my screenshot has been input manually. It's in the Line account setting:

Thank you

Florian

Translate
Level 2
Sep 24, 2019 3:36 PM UTC

Hello Florian,

I just hit the same issue, was this ever resolved?

Thanks,

Connor

Translate
Level 4
Sep 25, 2019 11:54 AM UTC

Hey Connor,

I'll dig more in this subjet early 2020, no news at the moment

Let me know if you find anything useful!

Thanks

Best regards

Florian

Edit: glad to know you have the same issue, at least it's not an individual problem

Translate