SSO by email for company server #1315
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
doubleface
approved these changes
Sep 8, 2025
zatteo
force-pushed
the
feat/sso-by-email
branch
from
47eb72a to
c440811
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using a company server, your previously needed to enter your Twake instance link which is not very user friendly.
Here we homogenize the behavior with our other apps (see cozy/cozy-pass-mobile#104 and cozy/cozy-keys-browser#359) with an autodiscovery mechanism based on a .well-known file so that we can only ask the company email.
We keep the login by url feature as a backup.
Checklist
Before merging this PR, the following things must have been done if relevant: