[Question] - use of "CookieSettings" for custom data about cloudfront-authorization-at-edge

[rpattcorner]

Thanks @ottokruse . Yes, the two parameters with JSON for cookie names and corresponding contents would solve the entire class of bootstrapping problem and maybe a few I haven't run into. Would all the lambdas need to be modified to set and propagate the custom cookie(s), or is there one particular Lambda that would be enough to pull the cookie thru to the SPA/Web App?

Wish I could do this now -- and hope you or others keep it in mind the next time the appropriate lambda(s?) come up for modification. It would go a long way towards making the framework (needs a name!) a generalized solution for SPA protection.

[ottokruse]

Hi @rpattcorner ,

perhaps they are a way to set behavioural metadata on already-defined cookies, and defining a new cookie would require modifying (all?) the lambdas to recognize and propagate the cookie end to end.

Yes

Is there a way to pass custom values into cookies all the way through the framework to the SPA that I'm just not seeing?

Can't think of a way

... that would be a terrific feature,

Yes, good idea.

General solution might be:

• Add 2 new parameters to the CF stack template:
  • "AdditionalCookieName" --> name of the additional cookie
  • "AdditionalCookieData" --> value of the additional cookie (put JSON in there if you want)
• In the Lambda@Edge code, read the "AdditionalCookieData" value and set it in a cookie with the name as specified by "AdditionalCookieName"

That would help you right? Thoughts?

[ottokruse]

Wish I could do this now -- and hope you or others keep it in mind the next time the appropriate lambda(s?) come up for modification. It would go a long way towards making the framework (needs a name!) a generalized solution for SPA protecti

Should be there now! Part of #75

Let me know how that works! Closing this issue for now

needs a name!

Any suggestions? I use "Auth@Edge" but I am too deep into this solution and can use an outside view