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 was working on a new deployment today and wanted to properly set up my config.json. Doing so the following question came up.
There is a property in the config.json with a RSA public key:
I suppose this is meant to be the pub key for the DAPS certificate?
With all prior deployments, even with an official AISEC certificate, i kinda ignored this line and it never broke anything.
Either way, if it IS supposed to be the DAPS cert pub key, then the default entry in the repository and the pub key you can extract from the localhost keystore dont match. Maybe the entry in config.json never changed, but the keystore was updated at some point?
So, i guess my question boils down to "Is this used in any way now or can i continue to ignore it?"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was working on a new deployment today and wanted to properly set up my config.json. Doing so the following question came up.
There is a property in the config.json with a RSA public key:
I suppose this is meant to be the pub key for the DAPS certificate?
With all prior deployments, even with an official AISEC certificate, i kinda ignored this line and it never broke anything.
Either way, if it IS supposed to be the DAPS cert pub key, then the default entry in the repository and the pub key you can extract from the localhost keystore dont match. Maybe the entry in config.json never changed, but the keystore was updated at some point?
So, i guess my question boils down to "Is this used in any way now or can i continue to ignore it?"
Beta Was this translation helpful? Give feedback.
All reactions