-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
When github secret is used there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github hook problems.
From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services).
Also a possibility to check secret from settings is good. JENKINS-33974
- is related to
-
-
- Resolved
-
[JENKINS-37956] Missing notification about request with bad secret for GitHub plugin
Ivan Tichý
created issue -
Ivan Tichý
made changes -
| Summary | Original: Missing notification about bad secret in log for GitHub plugin | New: Missing notification about request with bad secret in log for GitHub plugin |
Ivan Tichý
made changes -
| Summary | Original: Missing notification about request with bad secret in log for GitHub plugin | New: Missing notification about request with bad secret for GitHub plugin |
Ivan Tichý
made changes -
| Description |
Original:
When github secret is used, there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
New:
When github secret is used, there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github problems. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
Ivan Tichý
made changes -
| Link |
New:
This issue is related to |
Ivan Tichý
made changes -
| Description |
Original:
When github secret is used, there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github problems. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
New:
When github secret is used there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github problems. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
Ivan Tichý
made changes -
| Description |
Original:
When github secret is used there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github problems. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
New:
When github secret is used there in no info (e.g. in log) about unsuccessful request. It might be good also as warning for unauthorised attack. It can be listed in log or Github hook problems. From the Github side there is an icon showing whether the payload has been delivered (in webhooks and services). Also a possibility to check secret from settings is good. |
| Link |
New:
This issue relates to |
| Link |
Original:
This issue relates to |
Good point