Feature Suggestion
The certs used to connect to the gateway are now fixed on the client side. Because they certs are fixed, multiple clients cannot connect to one gateway. The client now can only connect to the gateway that uses the certs it generates.
To change this, we need to make the path for the certs used by the client a configurable one.
- Path become part of the client global conf.
- Path is updated when using
gateway generate-certs to that client's own certs.
- Path can be updated using new command
config certs.path
Impact
- This will allow users to use and reuse certs.
- This will allow multiple clients to connect to a single gateway.
- Path will be updated automatically when running
gateway generate-certs
Additional context
No response
Feature Suggestion
The certs used to connect to the gateway are now fixed on the client side. Because they certs are fixed, multiple clients cannot connect to one gateway. The client now can only connect to the gateway that uses the certs it generates.
To change this, we need to make the path for the certs used by the client a configurable one.
gateway generate-certsto that client's own certs.config certs.pathImpact
gateway generate-certsAdditional context
No response