gitlab-oauth-plugin | Jenkins authentication plugin using GitLab OAuth as source | Authentication library

by jenkinsci Java Version: gitlab-oauth-1.16 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | gitlab-oauth-plugin Summary

gitlab-oauth-plugin is a Java library typically used in Security, Authentication, Ruby On Rails applications. gitlab-oauth-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

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

Support

gitlab-oauth-plugin has a low active ecosystem.

It has 30 star(s) with 41 fork(s). There are 12 watchers for this library.

It had no major release in the last 12 months.

gitlab-oauth-plugin has no issues reported. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gitlab-oauth-plugin is gitlab-oauth-1.16

Quality

gitlab-oauth-plugin has no bugs reported.

Security

gitlab-oauth-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

gitlab-oauth-plugin is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gitlab-oauth-plugin releases are available to install and integrate.

Build file is available. You can build the component from source.

Top functions reviewed by kandi - BETA

kandi has reviewed gitlab-oauth-plugin and discovered the below as its top functions. This is intended to give you an instant insight into gitlab-oauth-plugin implemented functionality, and help decide if they suit your requirements.

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

Get all kandi verified functions for this library.

gitlab-oauth-plugin Key Features

No Key Features are available at this moment for gitlab-oauth-plugin.

gitlab-oauth-plugin Examples and Code Snippets

No Code Snippets are available at this moment for gitlab-oauth-plugin.

Community Discussions

Trending Discussions on gitlab-oauth-plugin

GitLab: Editing the merge request description triggers a merge request hook being sent

QUESTION

GitLab: Editing the merge request description triggers a merge request hook being sent

Asked 2019-Dec-18 at 14:12

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:

Request headers: ...

ANSWER

Answered 2019-Apr-02 at 12:25

Under 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)

Source https://stackoverflow.com/questions/55284986

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gitlab-oauth-plugin

You can download it from GitHub.
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 .