Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: email-ext-plugin
-
Labels:None
-
Environment:Jenkins LTS 2.46.1, EmailExtPlugin 2.57.1, role based matrix used
-
Similar Issues:
Description
After the latest update with the security patch, no mails sended anymore to "requester" of a job.
The error message in job console looks like this:
Not sending mail to user user@mail.com with no permission to view currentJob
When setting the suggested property
-Dhudson.tasks.MailSender.SEND_TO_USERS_WITHOUT_READ=true
it works.
The user has overall read permission (matrix based security setup) and for the conrete job the permission:
Job: View,Discover,Read,Workspace
Run: Update
The user has an account (if I click on the user which started the job .. also belongs to this job (can seen in the user view)) and the mail address is correct.
What permissions or settings are required to avoid this problem? We do not like to have this system property enabled.
Thanks for the great plugin and support!
Regards,
- Thomas
Attachments
Issue Links
- duplicates
-
JENKINS-9016 Git creates usernames based on 'name' not the email.
-
- Open
-
- is blocked by
-
JENKINS-46292 Issue when sending emails to Developers
-
- Closed
-
- is duplicated by
-
JENKINS-46292 Issue when sending emails to Developers
-
- Closed
-
- is related to
-
JENKINS-43268 Can't send email to registered users
-
- Closed
-
After many unsuccessful tries to give "unknown" users read access, I found this is the only way which essentially disables the security. In particular, I used the second one below and e-mail notification seem to be back to our normal. Bummer there isn't a better way. Also, it seems I only needed to do this on the master (which after digging, I found that modifying the jenkins.xml was the easiest way).
If the security fix is undesirable in a particular instance, it can be disabled with either or both of the following two system properties: