share-oauth-sso | Alfresco Share OAuth SSO Support | OAuth library

by gdepourtales Java Version: Current License: LGPL-3.0

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

kandi X-RAY | share-oauth-sso Summary

share-oauth-sso is a Java library typically used in Security, OAuth applications. share-oauth-sso has no bugs, it has no vulnerabilities, it has build file available, it has a Weak Copyleft License and it has low support. You can download it from GitHub.

The Alfresco OAuth SSO module lets users login in Alfresco Share using their Google Apps account. The module creates automatically accounts which do not exist to make Share and Google Apps integrate transparently. Configuration uses standard Share Surf configuration files. The jar is packaged with all dependencies so that it can be deployed as a single jar.

Support

Quality

Security

License

Reuse

Support

share-oauth-sso has a low active ecosystem.

It has 22 star(s) with 14 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 6 open issues and 3 have been closed. On average issues are closed in 409 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of share-oauth-sso is current.

Quality

share-oauth-sso has 0 bugs and 0 code smells.

Security

share-oauth-sso has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

share-oauth-sso code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

share-oauth-sso is licensed under the LGPL-3.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

share-oauth-sso releases are not available. You will need to build from source code and install.

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

Installation instructions, examples and code snippets are available.

share-oauth-sso saves you 476 person hours of effort in developing the same functionality from scratch.

It has 1122 lines of code, 139 functions and 9 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

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

Run the filter
Returns the class for the given name
Returns the root application context
Returns the URI to use for the Repository
Adds the ticket parameter to the request
Gets the human - readable name
Gets the family name
Gets the email address
Gets the OAuth service
Handle no request token without request token
Gets the user profile
Checks if a user exists
Process an OAuth token
Saves user
Checks if the user is valid
Performs an OAuth authentication process
Returns the configuration value for the given name
Gets the authentication ticket for the administrator user
Initializes the filter

Get all kandi verified functions for this library.

share-oauth-sso Key Features

No Key Features are available at this moment for share-oauth-sso.

share-oauth-sso Examples and Code Snippets

No Code Snippets are available at this moment for share-oauth-sso.

Community Discussions

Trending Discussions on share-oauth-sso

how to get a jar build in docker maven to my local repository

QUESTION

how to get a jar build in docker maven to my local repository

Asked 2017-Jan-26 at 16:14

I use a docker image of maven to build this custom Scribe, the simple OAuth Java lib

Scribe OAuth Java lib

...

ANSWER

Answered 2017-Jan-26 at 16:14

Left the jar build process out of the docker image build.

Why?

Because a better way to do this is making the maven docker image act as a single command:

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

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

Vulnerabilities

No vulnerabilities reported

Install share-oauth-sso

Create a Google API Access. Go to Google API Console and create your API (https://code.google.com/apis/console). II. Deploy the library. Copy the oauth-login-module jar in your Share webapp lib folder ([$WEBAPP_FOLDER]/share/WEB-INF/lib). III. Add the filter to web.xml. Add the following snippet to your Share web.xml before the filter named "Authentication filter". and add the following filter-mappings before the "Authentication Filter" mappings. IV. Configure the OAuth filter Add the following configuration to the share-config-custom.xml file. This file generally stands in the external configuration directory of Share. In the standard tomcat installation, the Share external configuration is located in tomcat/shared/classes/alfresco/web-extension directory. You can bypass the OAuthFilter by providing the bypassOAuth parameter to the share login page (example http://localhost:8081/share/page/?bypassOAuth).
Create a Google API Access
The project depends on a a modified java-scribe package available on github here : https://github.com/gdepourtales/scribe-java. The standard package build generates a shaded jar with dependencies included for easier deployment. The Maven has a webapp profile which builds an exploded share war. Running the "integration-test" launches the embedded jetty server with a custom web.xml and the filter deployed.

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: