#remix-auth/amplify-auth with Cognito User Pools?

1 messages · Page 1 of 1 (latest)

unkempt token
#

Has anyone got an example of this? It seems Cognito recommend using the amplify-auth library, but that seems to have its own session handling. I can't work out if I should:

a. use remix-auth and an appropriate strategy (form maybe?) with amplify-auth client implemented internally or
b. use amplify-auth and not bother with remix-auth/remix-session at all.

or maybe even c. just ignore the amplify-auth client altogether and use cognito as an oauth2 provider.

I'd appreciate any thoughts or opinions!

shadow bone
hallow hare
haughty birch
#

Are you already locked in on Cognito? I worked with it extensively on another project, and it's pretty heavy and annoying at times and has some limitations. And getting changes through to various libraries can literally take years.

I would look at 3-4 other options out there before considering Cognito (I'd probably roll my own auth before doing Cognito again haha) but if you already have users enrolled that's of course not an option.

hallow hare
haughty birch
#

Just my opinion, but... Steer clear off Amplify in its entirety. I did a large project on that and so many breaking changes and crazy stuff that took us so much time to keep up with. I can't count the number of times we had things breaking due to the core Amplify team changing stuff without considering it being breaking. And it took forever for them to fix it.

hallow hare
manic gorge
#

If you can use cognito independently of Amplify, then i would use remix-auth-oauth2 strategy.
I do that in my projects and it works very well.

hallow hare
vital light
#

but every time I've used it I've felt I was rebuilding a lot myself