Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Screenshots

...

  • You can configure projects to have their builds run with specified authorization.
  • Provides following ways to specify authorization.
    • Run as the user who triggered the build.
      • Does not work for scheduled, or polled builds.
      • Configuring projects are allowed only to users with the BUILD permission.
    • Run as anonymous.
    • Run as the specified user.
      • You are requested to enter the password of the specified user except following cases:
        • You are an administrator.
        • You are the specified user.
        • The specified user is not changed from the last configuration, and "No need for re-authentication" is checked.
          • This can threaten your Jenkins security. Be careful to use.
      • Configuring projects are allowed only to administrators and the user configured as the authorization.
        • "Don't restrict job configuration" allows other users (with the CONFIGURE permission) to configure the project. Ensure that only appropriate users have CONFIGURE permission for that project.
    • Run as SYSTEM
      • This is provided only to cancel the global configuration. SYSTEM authorization is often considered as "unconfigured", features provided by plugins may treat it as anonymous.
  • Provides an extension point to add new ways to specify authorization.

...

  • After installed Authorize Project plugin, you will find "Access Control for Builds" in "Manage Jenkins" > "Configure Global Security". Adding "Configure Build Authorizations in Project Configuration" enables Authorize Project plugin.
    • You can also disable specific strategies in this page. Disabled strategies are never used for authorization.
  • A new property side bar menu "Configure Build Authorization" will appear in project configuration pages.
    Image Added
  • You can select how to authorize builds of the project in the "Authorization" page.
    Image Removed Image Added
  • When selecting "Run as Specific User", you can enter User ID with whose authorization builds will run.
    Image Removed If you enter a user ID except yourself and have no administrative privilege, you are required to enter the password of that user.
    Image Removed Image Added
    • You can also use API token, especially for non password-based security realms.
  • Configuring project settings by unauthorized users are forbidden when you configure the authorization for the project. See #What's this? for details.
    Image Added

Extension point

A new way to authorize projects can be added with extending org.jenkinsci.plugins.authorizeproject.AuthorizeProjectStrategy, overriding the following method:

...

Version 1.2.2 (May 28, 2016)

...