Hello everyone!
I'm pretty excited to see this new networking workgroup formed and I'm very much looking forward to seeing what new stuff we get as a result.
One area that I was curious about was OAuth. This is a complex topic, for which there are numerous existing libraries. It isn't really networking exactly, but I'd definitely call it networking-adjacent.
Would a hypothetical OAuth library be something that could fall under the purview of the networking group? What about JWT?
Is the ask to develop one or to recommend one? I'd say JWT is largely solved, as is password hashing etc. OAuth is much more complex because any good library is either going to be tied to a client for a client library or tied to a server for a provider library.
No ask at all! I just wanted to get a handle on the workgroup's thinking thinking here.
Thank you!
It would be something we'd need to discuss. IMO it falls outside our charter, though there isn't really a good place for those kind of libraries to land. I think OAuth Provider libraries could be governed by the Server Workgroup, but I don't think a client library would really fall under that.
The ESG have spoken briefly about an incubation process, similar to what the SSWG did and that could be an avenue, but this is all personal opinion
OAuth is the kind of thing that definitely builds upon many of the networking building blocks that we're discussing and deeply interested in.
HTTP authentication as a topic I think is potentially in scope, although OAuth is a bit further from that, and I'd tend to agree that it's likely outside the charter.
Depending on community interest and engagement, I could see folks organizing something in this space as a consumer of those networking building blocks and the feedback from those efforts would be exceptionally valuable to the Networking WG's work items.