nexus3-external-auth-plugin | Sonatype Nexus3 Repository Manager

by hWorblehat Java Version: v0.1.2 License: MIT

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

kandi X-RAY | nexus3-external-auth-plugin Summary

nexus3-external-auth-plugin is a Java library. nexus3-external-auth-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.

This is a plugin for Sonatype Nexus OSS that allows authentication of externally defined users via JWTs and (to a certain extent) OpenID connect.

Support

Quality

Security

License

Reuse

Support

nexus3-external-auth-plugin has a low active ecosystem.

It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

nexus3-external-auth-plugin has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of nexus3-external-auth-plugin is v0.1.2

Quality

nexus3-external-auth-plugin has no bugs reported.

Security

nexus3-external-auth-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

nexus3-external-auth-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

nexus3-external-auth-plugin releases are available to install and integrate.

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

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

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

Converts a user to a user .
Generates a token .
Request an OAuth token .
Retrieves a JWT token from the servlet request .
Creates algorithm based on the specified algorithm string .
Retrieves the expiration date from the response .
Generate JWT .
Finds and returns the authorization info object .
Perform a HTTP GET request .
Create an OIDC authenticator with the given parameters .

Get all kandi verified functions for this library.

nexus3-external-auth-plugin Key Features

No Key Features are available at this moment for nexus3-external-auth-plugin.

nexus3-external-auth-plugin Examples and Code Snippets

No Code Snippets are available at this moment for nexus3-external-auth-plugin.

Community Discussions

No Community Discussions are available at this moment for nexus3-external-auth-plugin.Refer to stack overflow page for discussions.

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

Vulnerabilities

No vulnerabilities reported

Install nexus3-external-auth-plugin

The plugin can be installed just as any other Karaf bundle. See the Nexus documentation for more details. You can also take a look at the docker-compose.yaml file in the repository for a basic example.
Configure an OpenID Connect identity provider, and obtain a client ID and secret. If you want users to be able to use permanent JWT API keys, you need to enable use of the "on behalf of" flow so Nexus can obtain refresh tokens - ensure the token endpoint will accept the clients own access tokens as assertions. Activate the "External Realm (JWT and OpenID connect)" realm. Create a "JWT extract header" capability (Note: if enabling "on behalf of" authentication, this assumes the passed access token will be a JWT). Create an "OpenID Connect authentication" capability. Create roles matching the IDs that will be passed in the configured roles claim, with the desired permissions. Setup a reverse proxy in front of Nexus that performs the OpenID authentication. If you need to use permanent JWT API keys, have it pass an access token in the header configured above. Otherwise, just pass the ID token.
Configure an OpenID Connect identity provider, and obtain a client ID and secret. If you want users to be able to use permanent JWT API keys, you need to enable use of the "on behalf of" flow so Nexus can obtain refresh tokens - ensure the token endpoint will accept the clients own access tokens as assertions.
Activate the "External Realm (JWT and OpenID connect)" realm.
Create a "JWT extract header" capability (Note: if enabling "on behalf of" authentication, this assumes the passed access token will be a JWT).
Create an "OpenID Connect authentication" capability.
Create roles matching the IDs that will be passed in the configured roles claim, with the desired permissions.
Setup a reverse proxy in front of Nexus that performs the OpenID authentication. If you need to use permanent JWT API keys, have it pass an access token in the header configured above. Otherwise, just pass the ID token. Take a look at the docker-compose.yaml file in the repository for a basic example. To get it to work, you will need to copy deploy-conf/oauth2-proxy.example.conf to deploy-conf/oauth2-proxy.conf and change its content as appropriate.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: