Regarding first-party device IDs (FPID's) implementation, how can AEP Web SDK (which is a client side Javascript library) get the value of the cookie FPID even if FPID is flagged with HttpOnly?

[viniciuscosta1]

Hello, Hope you are all doing well!

I have a simple doubt:

Regarding first-party device IDs (FPID's) implementation, how is AEP Web SDK (being, as per the docs, a client side Javascript library) able to get the value of the cookie FPID to send to Edge network, even if the FPID is flagged with HttpOnly by the server? Wouldn't the browser block Web SDK, as a javascript library, to get FPID cookie?

Thank you very much!

[Anil_Umachigi · Accepted solution]

@viniciuscosta1 Have you tried doing this in an env? 

the configuration of FPID happens in datastream, this data is read on the edge server once enabled. 

if you do not want to go this way, you can read the cookie server side and update datalayer on client side before it's passed into identityMap 

read here 

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-i...