Adobe campaign Recipient crypted id - expiration | Community
Skip to main content
somasundaram_h
Community Advisor
Community Advisor
August 21, 2019
Solved

Adobe campaign Recipient crypted id - expiration

  • August 21, 2019
  • 5 replies
  • 6034 views

Team,

I checked and see that, there is a field in recipient called 'cryptedId' in AC console. I see that, this is generated using 'AESEncrypt(@id)' function. I want to know what is the expiration time for this value?

Because we're using this recipient id when we're sending link in the email delivery.

Thanks.

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

Hi,

AES encryption doesn't expire. I'm unaware of any hashing functions that expire.

If you want to expire cryptedId's, you can reload the data in recipient table. This will destroy information related to the id's, comprising the tables in this pic, along with any custom tables that use @recipient-id:

Thanks,

-Jon

5 replies

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
August 21, 2019

Hi,

AES encryption doesn't expire. I'm unaware of any hashing functions that expire.

If you want to expire cryptedId's, you can reload the data in recipient table. This will destroy information related to the id's, comprising the tables in this pic, along with any custom tables that use @recipient-id:

Thanks,

-Jon

somasundaram_h
Community Advisor
Community Advisor
August 22, 2019

Thanks Jon.

We're using the following to personalize the link.

<a href="http://server/webForm/APP264?&id=<%=escapeUrl(recipient.cryptedId) %>"> (reference:Publishing a web form  )

Is there any other methodology for the encryption other than AESEncrypt(@id)? What are the other methods that Adobe uses for encryption?

pablo_rosero1
Level 9
September 3, 2019

Thanks for your help, Jon. Check it out!

Jonathon_wodnicki
Community Advisor
Community Advisor
September 5, 2019

Hi,

What you have there is correct, though the escapeUrl() call is superfluous.

If you're trying to expire access, you can encrypt the current time with the id, then check it when loading the page, in link:

<a href="http://server/webForm/APP264?&id=<%= AESEncrypt(new Date().getTime() + ',' + recipient.id) %>">

Then after decrypting, split the value and check whether current time exceeds expiration threshold:

var timeId = decrypted.split(',');

if (timeId[0] < new Date().getTime() - DAYS_AGO * 86400 * 1000) logError(...);

Thanks,

-Jon

somasundaram_h
Community Advisor
Community Advisor
September 6, 2019

Hi Jon,

Thanks so much for your reply. Our client wanted to know the following things.

- Do we have expiration for the crypted id?

- Do we have any other method for encryption other than AES encryption method.

We checked in Adobe Campaign and see that,

- Each time when we send a link with recipient id, for each delivery, that will create a new crypted id for each recipient. That's the reason we raised this question here.

Thanks for your help!