-
-
Notifications
You must be signed in to change notification settings - Fork 214
feat: do not use HTTPS request for default instant onboarding #5618
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
Conversation
|
CI currently fails because of no core update. |
bf4246b to
27f45d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI also fails because there are still occurrences of DC_CHATMAIL_SERVER, namely in the GitHub workflow file.
Edit: also we don't have the var set in our repo's secrets / variables.
|
We have core 2.23.0 now, so once it is updated, this PR can be rebased. |
Depends on the core PR: <chatmail/core#7360> Using domain name in dcaccount scheme works similarly to existing scheme, but no HTTPS request is made and credentials are generated locally on the client.
27f45d2 to
b730096
Compare
WofWca
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure exactly what it does, but it's the Core's business. Looks good, the tests have been fixed.
Depends on the core PR: chatmail/core#7360
Using domain name in dcaccount scheme works
similarly to existing scheme,
but no HTTPS request is made
and credentials are generated locally on the client.