Simple CAS authentication for Rails, Sinatra or any Rack-based site

Provides a thin wrapper around the excellent ruby-openid gem from JanRan. gem version is unofficial, github fork of rails's by moro

Extended version of the Devise Database Authentication module to implement YubiKey OTP two factor authentication for registered users

This library allows Kerberos/GSSAPI authentication using either Basic method or Negotiate (i.e. authentication without the need of user/password combo).

The default authentication extension for Refinery CMS

A Ruby client for authentication in Cask CDAP services

A Ruby implementation of the Secure Remote Password protocol (SRP-6a). SiRP is a cryptographically strong authentication protocol for password-based, mutual authentication over an insecure network connection.

Hotwire compatible authentication for Ruby on Rails apps

Allows applictaions using Train to speak to Windows using Remote Management; handles authentication, cacheing, and SDK dependency management.

Docker v2 registry HTTP API client with support for token authentication

API Binding for OpenStack. With Swauth authentication for Swift

simple rails authentication

simple rails authentication

Plugin for the omnifocus gem to provide synchronization with Redmine Issues. This plugin uses the Redmine REST API. It must be enabled by an administrator for the plugin to work. The first time this runs it creates a yaml file in your home directory for the configuration data. * redmine_url is required. This is the base url for the redmine repository. * user_id is required. To find your user id login and go to the my account page. Your user_id is the number at the end of the url for my account. * username is optional. It is used if the redmine server requires authentication. * password is optional. It is used if the redmine server requires authentication. * queries is optional. It is used for custom queries or multiple queries. The queries config is an array of strings. The strings will be appended to a query of the form: "http://redmine_url/issues.xml?assigned_to_id=user_id" * just_project is optional. It is used to configure how to name the omnifocus projects used for issues. If just_project is true each redmine project will correspond to an omnifocus project. If it is false the omnifocus projects will be name with redmine_project-redmine_component. Example: --- user_id: 20 redmine_url: http://redmine/ username: me password: 1234 queries: ["status_id=1", "status_id=2"] just_project: false

SAML 2.0 is an XML-based protocol that uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, that is, an identity provider, and a SAML consumer, that is, a service provider. SAML 2.0 enables web-based authentication and authorization scenarios including cross-domain single sign-on (SSO), which helps reduce the administrative overhead of distributing multiple authentication tokens to the user.

This gem offers a shim to connect Rails apps with a Bonsai Elasticsearch cluster. The official Elasticsearch gem package requires some minor configuration tweaks in order to work correctly with Bonsai (namely the client needs to be instantiated with the cluster location and HTTP authentication details), and the process can be somewhat complicated for users who are unfamiliar with the system. The bonsai-elasticsearch-rails gem automatically sets up the Elasticsearch client correctly so users don't need to worry about configuring it in their code or writing an initializer. In order for the gem to work correctly, the application needs an environment variable called `BONSAI_URL`, which is populated with the complete Bonsai Elaticsearch cluster URL, including the HTTP authentication. The cluster URL will follow this pattern: https://user1234:pass5678@cluster-slug-123.aws-region-X.bonsai.io/ On Heroku, this variable is created and populated automatically when Bonsai is added to the application. Heroku users therefore do not need to perform any additional configuration to connect to their cluster after adding the bonsai-elasticsearch-rails gem. Users who are self-hosting their Rails app will need to make sure this environment variable is present: export BONSAI_URL="https://user1234:pass5678@aws-region-X.bonsai.io/" The cluster URL is available via the Bonsai dashboard.

Interface to the authentication token service

Token based authentication. To support backend authentication for ios, android, angular, ember etc...

A rails gem/plugin that handles authentication

A faye extension to add authentication mechanisms