gitlab-oauth-plugin | Jenkins authentication plugin using GitLab OAuth as source | Authentication library
kandi X-RAY | gitlab-oauth-plugin Summary
kandi X-RAY | gitlab-oauth-plugin Summary
The GitLab OAuth plugin provides a means of securing a Jenkins instance by offloading authentication and authorization to GitLab. The plugin authenticates by using a GitLab OAuth Application. It can use multiple authorization strategies for authorizing users. GitLab users are surfaced as Jenkins users for authorization. GitLab organizations and teams are surfaced as Jenkins groups for authorization. More comprehensive documentation is listed on the user documentation page.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Handles the user login
- Returns a proxy for the given HTTP method
- Build the redirect url
- Extracts the access token from the content
- Creates a new security components that will be used for GitLab authentication
- Get a user by username
- Load Group by name
- Get user details by username
- Returns true if the user has the given permission
- Create a git repository name from a URL
- Gets the name of the repository
- Gets the names of all the available repositories
- Get a list of projects belonging to the specified group
- Returns the text for GitLab
- Get the ACL for the project
- Handles commit login
- Removes all cached caches
- Returns the gitlab uri
- Convert a collection of repositories to their names
- Get a group by name
gitlab-oauth-plugin Key Features
gitlab-oauth-plugin Examples and Code Snippets
Community Discussions
Trending Discussions on gitlab-oauth-plugin
QUESTION
For my repository on GitLab I have a Merge Request Hook configured which triggers a build on a Jenkins CI machine. The hooks works as expected when a merge request is opened.
The webhook is configured with the following triggers:
- URL: https://example.com/project/ExampleApp_merge_requests
- Push events: Enabled
- Merge request events: Enabled
- Enable SSL verification: Off
Lately, when I edit the description of the merge requests then the hook also notifies the CI machine.
Here is an example POST request:
ANSWER
Answered 2019-Apr-02 at 12:25Under triggers (Settings -> integrations) perform the below:
- Enable push events (optional branch name - Branch is created via push events even before MR is possible)
- Enable MR event triggers in your project repo
This URL will be triggered when a merge request is created/updated/merged
In Jenkins Plugin configuration -
- Check "Push Events" (Any commits by way of direct Push or Creation)
- Un-check "Opened Merge Request Events"
- Check "Accepted Merge Request Events" (Any commits by way of Merge Request)
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gitlab-oauth-plugin
You can use gitlab-oauth-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the gitlab-oauth-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page