Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
I've created a project with the intention of using the Privacy Service APIs.
So i've made a few small tweaks:
1) Changed the endpoint to "https://platform.adobe.io/data/core/privacy/jobs?regulation=gdpr&size=100"
2) Changed requiredHeaders to include ['Authorization', 'x-api-key', 'x-gw-ims-org-id']
I've tried the request in Postman and it works fine, so I know there isn't an issue with the headers, but when I run it in localhost I get a 500 error:
Am I missing something obvious?
Edit: I didn't mention that I'm just using the sample app that gets generated, and then in index.js I've adjusted the requiredHeaders & apiEndpoint values:
Gelöst! Gehe zu Lösung.
Anhand von Themen werden Community-Inhalte kategorisiert und Sie können so relevanten Inhalt besser finden.
Zugriffe
Antworten
Likes gesamt
I am double-checking with some people to make sure there are no handy helper libs but essentially you will need to forward the headers from the action invoke to your secondary service call.
const res = await fetch(apiEndpoint,{
headers:{
"authorization": params.__ow_headers["authorization"],
"x-api-key": params.__ow_headers["x-api-key"],
"w-gw-ims-org-id": params.__ow_headers["w-gw-ims-org-id"],
"x-api-key": params.__ow_headers["x-api-key"]
}
})
Zugriffe
Antworten
Likes gesamt
Can you post a sample of the code in question? It is hard to tell the problem from that error message.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
I don't see an error in the code you posted.
In fact, I took the section of code you shared and ran it local and it worked fine.
500 could be coming from the privacy service. When you do the fetch on the privacy endpoint are you including all the needed headers, params, and auth needed to make that call?
const requiredParams = []
const requiredHeaders = ['Authorization','x-api-key','w-gw-ims-org-id']
const errorMessage = checkMissingRequestInputs(params, requiredParams, requiredHeaders)
if (errorMessage) {
// return and log client errors
return errorResponse(400, errorMessage, logger)
}
Zugriffe
Antworten
Likes gesamt
These are the debug statements I'm seeing:
I'm using Postman to make a request to the same endpoint with the same 4 headers (authorization, content-type, x-gw-ims-org-id and x-api-key) and header values, not seeing any issues.
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
So from the framework that was generated, the only things I've changed are row33 and row45
I'm using the 'generic' action name:
Zugriffe
Antworten
Likes gesamt
I am double-checking with some people to make sure there are no handy helper libs but essentially you will need to forward the headers from the action invoke to your secondary service call.
const res = await fetch(apiEndpoint,{
headers:{
"authorization": params.__ow_headers["authorization"],
"x-api-key": params.__ow_headers["x-api-key"],
"w-gw-ims-org-id": params.__ow_headers["w-gw-ims-org-id"],
"x-api-key": params.__ow_headers["x-api-key"]
}
})
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten