Hello
We have a need to authenticate the incoming streaming data from Adobe Launch into AEP. Without having to pass the client id/secret in the URL param, what the most optimized path to generate a token and then making the authenticated call to AEP.
Rajiv
Views
Replies
Total Likes
Hello @RajivKamath Create a serverless function in cloud of your choice. Do the token exchange securely in cloud function and use the cloud function endpoint in launch to push data to AEP.
Here are some cloud services you can use to create serverless functions.
GCP Cloud Functions: https://cloud.google.com/functions/docs/console-quickstart
Cloudflare worker: https://workers.cloudflare.com/
AWS Lambda: https://aws.amazon.com/lambda/
Hello @RajivKamath
Can you please clarify the need to authenticate via Adobe Launch? Are you attempting to post data into the AEP HTTP inlet?
Views
Replies
Total Likes
Yes, Bryan
Views
Replies
Total Likes
Can you please provide the use case of the need to ingest data via Adobe Launch and then send the data into a http streaming inlet.
You do have the ability to override the dataSetid which data is being written to via Adobe Launch. This could be an option to send data into a specific dataset instead of performing a /POST method with authentication.
Views
Replies
Total Likes
@RajivKamath i would suggest to use each layer separately, understanding is streaming data is at the Web layer
- use web layer for authentication
- once user authenticated, push required data element/date to data layer/launch , basically you will moving authenticated user data
- then stream it to AEP
Do not consider launch for any authentication activity.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies