I'm not overly familiar with SAML, but our plugin is based on this: https://github.com/bergie/passport-saml
Let us know if you find something relevant.
Hi @akurzawa, this would be quite a big feature, please open an issue if you have something precise in mind (a list of possible actions, what could trigger a workflow, ideally some use cases that couldn't be done without it, etc.). Also, a lot can probably already be done with XO's Web Hooks,
xo-cli and a third party workflow tool in between.
@sborrill I have a work-in-progress branch with a plugin for this: https://github.com/vatesfr/xen-orchestra/pull/4701
To test, you will need to checkout this branch, add a symlink to the
packages/xo-server-auth-http plugin into the directory
xo-server/node_modules and then to configure and unable the plugin from XO.
This will make basic authentication available with the path
/signin/basic, note that you can make it the default authentication by overriding
authentication.defaultSignInPage in your configuration file.
For now, all you get in the webhook request are the API call parameters and result (and a few other things). This is a generic behaviour that doesn't depend on what the call does. If you need some more specific information, your webhook handler can, for example, make a call to XO's API to fetch that information.