1
0
mirror of https://github.com/bitwarden/help synced 2025-12-18 17:23:31 +00:00
* tip - export format when uploading to a new account

* update on premise - cron example

* note on failed pin attempts

* strike email requirement for self-host licensing

* FAQ item on changing sp entity id, acs, callback path, etc.

* tips on --apikey for CLI in SSO required organizations

* issue 804
This commit is contained in:
fred_the_tech_writer
2021-11-17 10:50:42 -05:00
committed by GitHub
parent 4cb068e949
commit f32f7507d7
8 changed files with 43 additions and 7 deletions

View File

@@ -57,6 +57,10 @@ In practice, that means that anytime an employee logs in to Bitwarden using SSO,
- `https://vault.bitwarden.com/#/sso?identifier=your-org-id` for Cloud-hosted instances
- `https://your.domain.com/#/sso?identifier=your-org-id` for Self-hosted instances
### Q: How do I change pre-generated SSO configuration values?
**A:** Pre-generated SSO configuration values including **SP Entity ID**, **SAML 2.0 Metadata URL**, **ACS URL**, and **Callback Path** can be changed in self-hosted environments by changing the `url:` value in `.bwdata/config.yml` and running the `./bitwarden.sh rebuild` command to apply your change.
## Security
### Q: How does Login with SSO work with the zero-knowledge model?