Setup SSO with ory.sh
First service to be migrated to (via Saml or OIDC) should be Bitwarden
What does that mean? We have not BW service AFAIK
What does that mean? We have not BW service AFAIK
We do (for the backup service) and we will have to relaunch it (maybe with an onprem instance), ticket to follow.
But ory.sh should be ready to get OIDC/SAML requests anyway.
We do (for the backup service) and we will have to relaunch it (maybe with an onprem instance), ticket to follow.
Not our service. We use the SaaS version with one (actually two) backup-dedicated Free accounts. Maybe we want to have shared BW secrets for the team and would use SSO to connect to BW's SaaS or we could setup our own BW and use SSO to access it in the same manner.
Either way it's not a service to migrate (from our POV) ory.sh must be setup indeed and tested. FYI BW supports both SAML and OIDC.
Should you want to extend borg-backup's behavior, a ticket there would be needed.