You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using my certificate from task warrior to handle this. I wish I could change this parameter within the configuration file to point to the given file instead of the hard-coded public_key.pem or private_key.pem files.
Maybe I'm holding it wrong, but if otherwise, it should be documented.
Thanks anyway,
best regards
The text was updated successfully, but these errors were encountered:
Your answer surprises me a bit, considering the fact that you're using JWT, which requires asymmetric types of keys.
As long your certificate is x509 compilable, this shouldn't be much of a concern. PEM files are just a coding format to contain the x and y ( y which is often quite static away) parameters of your asymmetric keys, with some additional PKI information. What is relevant for us at this stage is the key/certificate.
So, it might be necessary to add also key size and format to the configuration?
I might need to review your usage of JWT. So far, it seems to more like you copy and pasted the default example with slight adjustments.
HI,
First of all, thanks for this project!
I'm using my certificate from task warrior to handle this. I wish I could change this parameter within the configuration file to point to the given file instead of the hard-coded
public_key.pem
orprivate_key.pem
files.Maybe I'm holding it wrong, but if otherwise, it should be documented.
Thanks anyway,
best regards
The text was updated successfully, but these errors were encountered: