Invalid redirect parameter | HTTP 400 when starting Google sign_in about sso

[omerxx]

Hey @Jusshersmith just published my post helping ppl integrating the same way I did.
Hope it helps and maybe @buzzfeed-api finds something in it...
https://dev.to/omerxx/introduction-to-zero-trust-on-aws-ecs-fargate-38bl

[omerxx]

I found the solution by going through with the Google provider setup steps 3,4 - although they clearly state it is only relevant if a granularity of groups and users is required. Once I loaded credentials.json I was able to login.
Still, I cannot understand the reason for it not being able to function with just client_id and secret_id.

This project is really awesome, but it lacks clear documentation. Would be happy to help improve it if I can get a point of communication.

[Jusshersmith]

Hey @omerxx,

Thank you for submitting this, and I'm sorry for the difficulties you've faced; I appreciate you sticking with it and working through the problem though!

While I haven't yet found the time to dig into this, I wanted to respond and at least acknowledge this. We need to clarify whether it's the documentation that's incorrect or the logic -- I'm not convinced at this point that it isn't the logic itself, though it needs some further investigation either way.

Separately, I agree that parts of the documentation could benefit from some extra clarity! This is definitely something I'd like to invest some time in. Any contributions are welcome and appreciated as always 🙂

[omerxx]

@Jusshersmith I appreciate your response.
Not really sure either as this came down to trail and error.
Working on a blog post that will describe my real-life experience with implementing everything on ECS.
If I'll find time to incorporate a list of optional & mandatory configuration variables, I'll make sure to make a PR out of it.

Thanks again :)