Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17144

Add documentation for GithubAuthorizationStrategy

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • swarm-plugin
    • None
    • 3.26

      CLI supports login via key pairs, it would be nice to be able to use the same solution for swarm plugin.

          [JENKINS-17144] Add documentation for GithubAuthorizationStrategy

          I've run into the situation with GithubAuthorizationStrategy from github-oauth where the CLI must use an ssh key pair to function (-username/-password do not work – it's not clear to me if this is an issue with CLI or the authorization strategy). However, swarm clients can not presently use an ssh key pair. After some thrashing around, I've discovered that swarm clients will function with the API token as the password for a user. However, the user account has to be created and the API token retrieved before clients can be configured. This is both non-orthogonal with how the CLI must authenticate and sub-optimal for configuration management.

          Joshua Hoblitt added a comment - I've run into the situation with GithubAuthorizationStrategy from github-oauth where the CLI must use an ssh key pair to function (- username/ -password do not work – it's not clear to me if this is an issue with CLI or the authorization strategy). However, swarm clients can not presently use an ssh key pair. After some thrashing around, I've discovered that swarm clients will function with the API token as the password for a user. However, the user account has to be created and the API token retrieved before clients can be configured. This is both non-orthogonal with how the CLI must authenticate and sub-optimal for configuration management.

          Oleg Nenashev added a comment -

          KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Basil Crow added a comment -

          See the workaround in JENKINS-48708.

          Basil Crow added a comment - See the workaround in JENKINS-48708 .

          Basil Crow added a comment -

          While a workaround exists, I think the user experience could be improved, or at least better documented. I'll have to think more about how best to achieve this.

          Basil Crow added a comment - While a workaround exists, I think the user experience could be improved, or at least better documented. I'll have to think more about how best to achieve this.

          Basil Crow added a comment -

          I recently wrote some new documentation on how to configure Swarm authentication and authorization, covering matrix-based security, project-based Matrix Authorization Strategy, and Role-Based Strategy. I would love to see additional documentation for github-oauth's GithubAuthorizationStrategy, ideally with accompanying tests in hudson.plugins.swarm.AuthorizationStrategyTest. However, I am personally unfamiliar with github-oauth or how to use it. PRs are welcome!

          Basil Crow added a comment - I recently wrote some new documentation on how to configure Swarm authentication and authorization, covering matrix-based security, project-based Matrix Authorization Strategy, and Role-Based Strategy. I would love to see additional documentation for github-oauth 's GithubAuthorizationStrategy , ideally with accompanying tests in hudson.plugins.swarm.AuthorizationStrategyTest . However, I am personally unfamiliar with github-oauth or how to use it. PRs are welcome!

          Basil Crow added a comment -

          Documentation was added by jimklimov in jenkinsci/swarm-plugin#319

          Basil Crow added a comment - Documentation was added by jimklimov in jenkinsci/swarm-plugin#319

            jimklimov Jim Klimov
            mbarr Matthew Barr
            Votes:
            8 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: