Introduce a new endpoint, /jwks, which returns a JSON Web Key Set (JWKS). This set of public crypto keys will be used by external parties to encrypt data intended for our backend. In the context of the resource server, this key will be used by the authorization server to encrypt the introspection response. The current implementation exposes a single public key, with the private key configurable in the app settings. The private key is represented as a string. For enhanced security, we might prefer to store this data in a .pem file excluded from version control. A few parameters for this key, such as its type and encoding, are configurable in the settings. A critique of the current design is its lack of extensibility. If we decide to offer more than one encryption method, this view will require refactoring. Additionally, the current implementation is tightly coupled with joserfc. This lays the foundation for further improvements. Please note, this endpoint only public components of the key, there is no chance for any secret leaking.