What do you think of implementing a CLI around go-auth2 [maybe with a bunch of command-line args and/or env vars and/or config file] such that oauth2 implementations can have something to test their implementation against.
Your codebase seems like a good candidate, seeing as it's maintained, written in Go (static independent binaries + cross-platform FTW), permissively licensed, and has self-contained example code (unlike other approaches like Rust's oxide-auth which are more middleware than self-contained).
I'm writing a little very cross-platform handler in C (C89) for oauth2 exchange via the redirect_uri (hosts a local simple native socket server). In the short term I have no intention of writing my own oauth2 server (though I did 8 years ago in Python for an earlier RFC6749 draft).
So what do you think? - I might even contribute if there's interest…
What do you think of implementing a CLI around go-auth2 [maybe with a bunch of command-line args and/or env vars and/or config file] such that oauth2 implementations can have something to test their implementation against.
Your codebase seems like a good candidate, seeing as it's maintained, written in Go (static independent binaries + cross-platform FTW), permissively licensed, and has self-contained example code (unlike other approaches like Rust's oxide-auth which are more middleware than self-contained).
So what do you think? - I might even contribute if there's interest…
Thanks for your consideration