This sets the file format to be yaml instead of let the config to figure
it out by extension. The problem is that it guesses file format by
extension and some tools - eg ansible - create tempfiles without
extension to validate the config changes before applying them, that
makes the validation always fail.
This PR changes how the config file is loaded so that it doesn't guess
file type.
---------
Co-authored-by: Eugene <inbox@null.page>
When a target is deleted from the admin UI, any associated SSH known
hosts entries are now also removed. This prevents orphaned host key
entries from remaining in the database after a target is deleted, which
could cause confusion if a new target with the same hostname is created
later.
closes: #1251
Signed-off-by: Chinmay D. Pai <chinmaydpai@gmail.com>
Currently Warpgate implements openidconnect_rs in a way where the OIDC
audience has to be either just the warpgate client id or you have to
explicitly trust every additional client id. Some IdP's
([ZITADEL](https://zitadel.com/) in my case) however don't let you limit
the audience for a specific client on the IdP side, and in my usecase
clients in the IdP project are often added or removed. Having to update
the warpgate config every time this happens is undoable for me, as such
I would like to explicitly trust any unknown client via config.
This PR implements that via an added optional setting
(`trust_unknown_audiences`) for the OIDC-custom provider.