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

Disabled registration notification e-mail in ldap + reverse proxy mode #21348

Closed
wants to merge 3 commits into from

Conversation

pboguslawski
Copy link
Contributor

Disabled registration notification e-mail in ldap + reverse proxy mode to avoid
spamming user with invalid instructions (such accounts are created by admin
in LDAP not during self registration and no gitea passwords are used for auth).

Related: #18601
Author-Change-Id: IB#1122610

Disabled registration notification e-mail in reverse proxy mode to avoid
spamming with invalid instructions (such accounts are created by admin
in exteral systems not during self registration and no gitea passwords
are used for auth).

Related: go-gitea#18601
Author-Change-Id: IB#1122610
Fixes: 7b9435e
Author-Change-Id: IB#1122610
@wxiaoguang
Copy link
Contributor

It looks good to me. According to the comment: SendRegisterNotifyMail triggers a notify e-mail by admin created a account., then the SendRegisterNotifyMail shouldn't be called for accounts created by other methods. The email only contains links for "login" and "forget password", which doesn't make sense in other cases.

And beside the LDAP and ReverseProxy mode, there seems to be more calls to it (pam/sspi/smtp), should these calls also be removed together?

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 5, 2022
@pboguslawski
Copy link
Contributor Author

pboguslawski commented Oct 6, 2022

And beside the LDAP and ReverseProxy mode, there seems to be more calls to it (pam/sspi/smtp), should these calls also be removed together?

This mod was checked with reverse proxy+ldap scenario only and we don't use/test other cases. Feel free to adjust other auth backends also if appropriate in other PRs.

@wxiaoguang
Copy link
Contributor

Replaced by Do not send "registration success email" for external auth sources #24632

@wxiaoguang wxiaoguang closed this May 10, 2023
@pboguslawski pboguslawski deleted the main-IB#1122610 branch May 22, 2023 12:57
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Aug 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants