Safari Browser does not store ApiGateway + S3 app login cookie because this architecture leads to SameSite: None attribute

0

My app has its back-end on API Gateway and front-end is on a S3 bucket. That means they have different URLs and the cookie ends up being samesite: None. Because of that, Safari Browser doesn't store the login cookie I send from the back-end even with secure: true.

My question is, is it possible to mantain this architecture and still manage to send a cookie that Safari can store ? If not possible, what would the architecture look like to be able to send cookies samesite: true ? If you can point me to the right direction I appreciate it.

No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions