Dominik Thalhammer

C++17 introduced `__has_include` to check if an include path is valid. For everything before that the best option is probably a preprocessor macro to switch between both, which could be...

> The lack of a C++ ecosystem is to blame for that More like the abundance of the same. Unlike most "cool new" programming languages, which have a single established...

While this was how it worked originally, jwt-cpp has come a long way since then (supporting multiple ssl and json libraries in multiple versions). The supposed way to do this...

Hi, While I absolutely think those might give a great addition without to much added stuff, I honestly don't have the time right now to read through and implement those....

Loading keys from jwk and jwks is definitly something I'd like to support in the future. I don't personally like jwks much because it is an invitation to loading untrusted...

Hi, jwt-cpp doesn't support Unicode, because JWT's are defined to use UTF-8. UTF-8 is generally useful for these kinds of tasks because it is equivalent to ASCII for most of...

AFAIK codecvt is only used to convert between lower/upper-case strings to provide case insensitive matching. We could fall back to [std::tolower](https://en.cppreference.com/w/cpp/string/byte/tolower) with the caveat that it might not match correctly...

> Seem like every new year we break support for this compiler #118 laughing Maybe we should consider adding a "laoshanxi Test" to the CI ? ;)

The jwks part in jwt-cpp is very much in it's early stages, which is one of the reasons its not really announced as a feature anywhere yet. Whats there should...

Technically any jwt token with any padding at all is invalid. [RFC7515](https://www.rfc-editor.org/rfc/rfc7515.txt) makes this pretty clear: > Base64 encoding using the URL- and filename-safe character set defined in Section 5...