Skip to content
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.

Why not oauth4webapi? #122

Open
ajmcmiddlin opened this issue Dec 17, 2023 · 0 comments
Open

Why not oauth4webapi? #122

ajmcmiddlin opened this issue Dec 17, 2023 · 0 comments

Comments

@ajmcmiddlin
Copy link

On the face of it, it appears that this project and oauth4webapi have the same goals. Is there a reason to use one library over the other, or some important differences to be aware of?

In case this comes across as overly blunt or accusatory, I'm new to remix and server-side JS land and really just trying to understand the landscape while making library choices.

Context

I'm looking to implement OIDC with PKCE in a remix application. I came across a PR on remix-auth-oauth2 to add PKCE support and there's a comment there suggesting the use of this library. From earlier research I'd found oauth4webapi, which is (from the docs at least) certified, webapi based implementation of the openid-connect library that this is porting. Given there's already a certified webapi client to build on top of, that seems like the place to start (for my needs at least) when building a remix auth strategy, but I'm wondering if I've missed something.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant