Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup SSO with ory.sh #90

Open
kelson42 opened this issue Jul 21, 2023 · 3 comments
Open

Setup SSO with ory.sh #90

kelson42 opened this issue Jul 21, 2023 · 3 comments
Labels

Comments

@kelson42
Copy link
Contributor

First service to be migrated to (via Saml or OIDC) should be Bitwarden

@kelson42 kelson42 added the task label Jul 21, 2023
@rgaudin
Copy link
Member

rgaudin commented Jul 21, 2023

What does that mean? We have not BW service AFAIK

@kelson42
Copy link
Contributor Author

kelson42 commented Jul 21, 2023

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.

@rgaudin
Copy link
Member

rgaudin commented Jul 21, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants