What does this implement/fix? Explain your changes.
This authentication layer is something good to have that can be used by any of the microservices, it just needed to set the AUTHENTICATION_KEY environment variable with the API Key desired, which will be used to authenticate requests against the X-API-Key header.
The env var ENDPOINTS_WHITELISTED can be used to whitelist endpoints - it may contain a comma-separated-list of endpoints and is able to accept regex.
At the moment this capability is configured only for nightfall-client, since it is likely that a deployer/enterprise wants to use this layer to protect the application endpoints.
This change implies changes in SDK so that the calls can be authenticated.
What does this implement/fix? Explain your changes.
This authentication layer is something good to have that can be used by any of the microservices, it just needed to set the
AUTHENTICATION_KEY
environment variable with the API Key desired, which will be used to authenticate requests against theX-API-Key
header. The env varENDPOINTS_WHITELISTED
can be used to whitelist endpoints - it may contain a comma-separated-list of endpoints and is able to accept regex. At the moment this capability is configured only fornightfall-client
, since it is likely that a deployer/enterprise wants to use this layer to protect the application endpoints.This change implies changes in SDK so that the calls can be authenticated.
Does this close any currently open issues?
No
What commands can I run to test the change?
A new test was added to Github Action
Any other comments?
No