github-plugin icon indicating copy to clipboard operation
github-plugin copied to clipboard

[JENKINS-66931] GitHub hook trigger not working after SAML enabled

Open jenkins-infra-bot opened this issue 4 years ago • 0 comments

Hi,

We found GitHub hook trigger for GITScm polling is not working after SAML 2.0 enabled.
Here's the steps to reproduce it:

  1. Go to configure and make sure Jenkins Security Realm is Jenkins’ own user database.
  2. Open a PR from GitHub and make sure can trigger a Job normally.
  3. Enable SAML 2.0
  4. Open a PR from GitHub
  5. Trigger Job failed, but doesn't receive any error message

Here's the version Info:
  - Jenkins version: 2.289.2
  - SAML plugin: 2.0.8
  - SAML Single Sign On(SSO): 1.0.5 
  - Github plugin: 1.32.0
  - github-api plugin: 1.117
  - github-branch-source plugin: 2.9.3
  - github-pr-comment-build plugin: 2.3
  - pipeline-github-lib plugin: 1.0
Best Regards,

Alex


Originally reported by alexsu_17media, imported from: GitHub hook trigger not working after SAML enabled
  • assignee: lanwen
  • status: Open
  • priority: Minor
  • component(s): github-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-08
Raw content of original issue

Hi,

We found GitHub hook trigger for GITScm polling is not working after SAML 2.0 enabled. Here's the steps to reproduce it:

  1. Go to configure and make sure Jenkins Security Realm is Jenkins’ own user database.   2. Open a PR from GitHub and make sure can trigger a Job normally.   3. Enable SAML 2.0   4. Open a PR from GitHub   5. Trigger Job failed, but doesn't receive any error message

Here's the version Info:   - Jenkins version: 2.289.2   - SAML plugin: 2.0.8   - SAML Single Sign On(SSO): 1.0.5    - Github plugin: 1.32.0   - github-api plugin: 1.117   - github-branch-source plugin: 2.9.3   - github-pr-comment-build plugin: 2.3   - pipeline-github-lib plugin: 1.0 Best Regards,

Alex

jenkins-infra-bot avatar Oct 19 '21 03:10 jenkins-infra-bot