Hello,
I am using cURL to test sending calls to the Adobe Edge Network server API. In the past, I have been able to use Assurance to generate a "debug session id" that allowed me to send requests from cURL through Assurance.
However, it now seems that Assurance now requires that you set up an app with the Assurance SDK first: https://experienceleague.adobe.com/docs/experience-platform/assurance/view/event-transactions.html?l...
When I create a session, I can generate a "adb_validation_sessionid", but when I attach the ID to cURL requests events don't show up in the session.
Am I no longer able to use Assurance with simple cURL requests/outside of the SDK?
Any input appreciated. Thank you.
解決済! 解決策の投稿を見る。
表示
返信
いいね!の合計
@williamh3207805 , here is another suggestion "You could create an assurance session, get the validation token from the “copy link” button to start the session, then find a way to either add a adobeAepValidationToken=<token> query param to the outgoing api calls or a X-Adobe-AEP-Validation-Token header with the token as the header value."
Please let me know if this works for you.
表示
返信
いいね!の合計
Hi @williamh3207805 ,
It's not correct that you need to set up an app with the Assurance SDK. For example, we use Assurance all the time with Web SDK implementations (which don't require implementing any Assurance SDK). With Web SDK, we can initiate the Assurance session from within the Experience Platform Debugger. This documentation just currently has an assumption that Assurance is for mobile app implementations and not all Edge implementations. Unfortunately, I am not sure of the process to initiate a session using the Server API, but I will see what I can find out and will share here. I'll also open a ticket for the documentation team.
Thank you - much appreciate you looking into this.
表示
返信
いいね!の合計
@williamh3207805 , does the suggestion in this thread help?
表示
返信
いいね!の合計
@williamh3207805 , here is another suggestion "You could create an assurance session, get the validation token from the “copy link” button to start the session, then find a way to either add a adobeAepValidationToken=<token> query param to the outgoing api calls or a X-Adobe-AEP-Validation-Token header with the token as the header value."
Please let me know if this works for you.
表示
返信
いいね!の合計
Thank you! Both methods work: adding a adobeAepValidationToken parameter or the X-Adobe-AEP-Validation-Token header.
It would be great to get this added to the documentation at some point.
In any case, I have what I need for debugging - thank you again.
表示
返信
いいね!の合計
@williamh3207805 Did you find the suggested solutions helpful? It would be great if you can mark the answer as correct for posterity. If you have found out solution yourself, share it with wider audience in the community.