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
The location of local CA certificates is not standardised across the various operating systems, which means that in order for a developer to use a custom certificate, they need to explicitly configure the Node.js https.Agent:
Configuring Node.js can be quite challenging for developers, so being able to specify certificates as part of the regular Serenity/JS configuration could contribute to a better developer experience.
How would you like to solve it?
We could make CallAnApi accept a configuration object with additional rejectUnauthorized, cert, and key properties, and then configure the https.Agent based on those properties:
What's the problem you're trying to solve?
The location of local CA certificates is not standardised across the various operating systems, which means that in order for a developer to use a custom certificate, they need to explicitly configure the Node.js
https.Agent
:Configuring Node.js can be quite challenging for developers, so being able to specify certificates as part of the regular Serenity/JS configuration could contribute to a better developer experience.
How would you like to solve it?
We could make
CallAnApi
accept a configuration object with additionalrejectUnauthorized
,cert
, andkey
properties, and then configure thehttps.Agent
based on those properties:For example:
Another advantage of extending the configuration to allow for
cert
,key
, andrejectUnauthorized
is that it would support implementing #594Are there any alternatives?
Developers can specify a custom ability to
CallAnApi
using anhttps.Agent
configured to accept their certificates:How can we make it happen?
The text was updated successfully, but these errors were encountered: