JWK key ring URL does not support "file://"

[Molive-0]

I'm setting up a lore server on a server with a few friends. As it is open to the public, I'm trying to implement authentication.

I've never used JWK/JWT before, and don't have a separate server for hosting any of it. As such, I've used step to generate some keys and tokens, which are stored on the same machine as the lore server.

However, it appears that the keyring must be hosted at a URL. It seems that it also does not support "file://" URLs. Therefore, I have to try and publicly host the keyring, which is causing no end of certificate errors.

Is it possible to load the keyring from a local file? If not, can that feature be added? Or have I just entirely misunderstood how JWT/JWK works?

[kidskoding]

JWK's endpoint supports a plain String in its HTTP GET request via reqwest, which means only pure urls via HTTP/HTTPS will work. so yeah, a file:// URL will just fail the HTTP request since there's no way to read from disk.

Is it possible to load the keyring from a local file?

no. i reproduced this situation, verifying it's not possible, via a test that tries to read keys from a local file, and confirmed it fails before ever reaching the file at all, regardless of whether or not the file exists (see below)

fixing this simply involves checking the scheme of the endpoint - if http or https, already taken care of. However, if a file, have the file read straight off the disk instead of sending it over via network. both paths result in the same outcome, where they give the same JSON key

[kidskoding]

PR attached above. PR is of course just one proposed implementation. Open to discussion with maintainers on whether this approach is suited long term, or if it is better to switch to a separate config field to keep network and file config explicitly distinct