1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
So finally I got it to work like this. Instead of overriding the whole response, I only overrode the event.response.claimsOverrideDetails:
exports.handler = async (event, context) => {
event.response.claimsOverrideDetails = {
"claimsToAddOrOverride": {
"attribute_key2": "attribute_value2",
"attribute_key": "attribute_value"
}
};
return event
};
beantwortet vor einem Jahr
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
This probably doesn't help, but I had the same issue until I added a 'return event;' after the callback. The weird thing is that it now still works even when I take out the return line.
Thanks @rePost-User-7943174 I have tried your approach but I still got the same error.
After calling
callback(null, event)
I added the statementreturn event
but it lead to the same error