rubycas-server | Provides single sign-on authentication for web | Authentication library

by rubycas Ruby Version: Current License: Non-SPDX

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

kandi X-RAY | rubycas-server Summary

rubycas-server is a Ruby library typically used in Security, Authentication applications. rubycas-server has no bugs, it has no vulnerabilities and it has low support. However rubycas-server has a Non-SPDX License. You can download it from GitHub.

Provides single sign-on authentication for web applications, implementing the server-end of Jasig's CAS protocol.

Support

Quality

Security

License

Reuse

Support

rubycas-server has a low active ecosystem.

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

It had no major release in the last 6 months.

There are 47 open issues and 61 have been closed. On average issues are closed in 142 days. There are 19 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of rubycas-server is current.

Quality

rubycas-server has 0 bugs and 0 code smells.

Security

rubycas-server has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

rubycas-server code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

rubycas-server has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

rubycas-server releases are not available. You will need to build from source code and install.

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

rubycas-server saves you 1268 person hours of effort in developing the same functionality from scratch.

It has 2850 lines of code, 137 functions and 50 files.

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

Top functions reviewed by kandi - BETA

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

Logs out a controller action .
Sends static file to serve a static file
Serializes an extra value .
Provides the status code for the response
Checks if the service is allowed
Returns true if the given service is valid .
Creates a new Message object .

Get all kandi verified functions for this library.

rubycas-server Key Features

No Key Features are available at this moment for rubycas-server.

rubycas-server Examples and Code Snippets

No Code Snippets are available at this moment for rubycas-server.

Community Discussions

Trending Discussions on rubycas-server

Infinite redirects with Devise and devise_cas_authenticatable

QUESTION

Infinite redirects with Devise and devise_cas_authenticatable

Asked 2018-Mar-07 at 11:57

I have a Rails 5.2 app that uses Devise 4.4.1 and devise_ldap_authenticatable for auth. I'm trying to switch that out for devise_cas_authenticatable and now get into a redirect loop after entering my credentials on the CAS login page.

The app, the CAS server (rubycas-server), LDAP and the database are all running as Docker containers through Docker Compose. The CAS server is configured to use HTTP for development.

From what I can tell, my app isn't setting a session when CAS returns after logging in, but I have no idea why. Even some pointers for debugging would be gratefully received.

Here is the section of the log that repeats with each redirect:

...

ANSWER

Answered 2018-Mar-07 at 11:57

The problem occurred when devise_ldap_authenticatable called resource.save. Validations run before the before_create callback, and these validation errors were silently preventing the user from being created and thus authenticated. The uniqueness validation on the email field is why the log shows a SELECT by email.

The solution was to change

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

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

Vulnerabilities

No vulnerabilities reported

Install rubycas-server

Example with mysql database:. Your RubyCAS-Server should now be running. Once you've confirmed that everything looks good, try switching to a Passenger deployment. You should be able to point Apache (or whatever) to the rubycas-server/public directory, and everything should just work. Some more info is available at the RubyCAS-Server Wiki. If you have questions, try the RubyCAS Google Group or #rubycas on freenode.
git clone git://github.com/rubycas/rubycas-server.git
cd rubycas-server
cp config/config.example.yml config.yml
Customize your server by modifying the config.yml file. It is well commented but make sure that you take care of the following: Change the database driver to mysql2 Configure at least one authenticator You might want to change log.file to something local, so that you don't need root. For example just casserver.log You might also want to disable SSL for now by commenting out the ssl_cert line and changing the port to something like 8888
Create the database (i.e. mysqladmin -u root create casserver or whatever you have in config.yml)
Modify the existing Gemfile by adding drivers for your database server. For example, if you configured mysql2 in config.yml, add this to the Gemfile: gem "mysql2"
Run bundle install
bundle exec rubycas-server -c config.yml

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: