The status quo is that you have to search for the CID you are working with every time you launch the Toolkit if you are an MSSP customer. This change allows you to specify the CID in either an environment variable or as a command line option (--cid).
This change is also available generically to other auth backends should they be available in the future.
Additionally, by passing the Click Context through to the authenticate() function, we pave the way for other parameters to be passed through to authentication backends in the future if required.
Note that we have a breaking change here. The only supported environment variable to set the CID for an auth backend that supports it (like the MSSP one) will be FALCON_TOOLKIT_CID. The other (FALCON_MSSP_CHILD_CID) has been removed, since it wasn't consistent and the new one is simpler and generalised. Apologies for any inconvenience caused.
The status quo is that you have to search for the CID you are working with every time you launch the Toolkit if you are an MSSP customer. This change allows you to specify the CID in either an environment variable or as a command line option (
--cid).This change is also available generically to other auth backends should they be available in the future.
Additionally, by passing the Click Context through to the
authenticate()function, we pave the way for other parameters to be passed through to authentication backends in the future if required.Note that we have a breaking change here. The only supported environment variable to set the CID for an auth backend that supports it (like the MSSP one) will be
FALCON_TOOLKIT_CID. The other (FALCON_MSSP_CHILD_CID) has been removed, since it wasn't consistent and the new one is simpler and generalised. Apologies for any inconvenience caused.