Install authlogic

To use the reference documentation, you must understand how Authlogic's code is organized. There are 2 models, your Authlogic model and your ActiveRecord model:. Let's walk through a typical rails setup. If you want to enable all the features of Authlogic, a migration to create a User model might look like this:.

As you can see, this fits nicely into the conventional controller methods. The SameSite attribute tells browsers when and how to fire cookies in first- or third-party situations. SameSite is used by a variety of browsers to identify whether or not to allow a cookie to be accessed. Up until recently, the standard default value when SameSite was not explicitly defined was to allow cookies in both first- and third-party contexts.

Note that when setting SameSite to None, the secure flag must also be set secure is the default in Authlogic. See Authlogic::TestCase. If you create one of your own, please let us know about it so we can add it to this list. Or just fork the project, add your link, and send us a pull request.

Interested in how all of this all works? Think about an ActiveRecord model. A database connection must be established before you can use it.

In the case of Authlogic, a controller connection must be established before you can use it. It uses that controller connection to modify cookies, the current session, login with HTTP basic, etc. It connects to the controller through a before filter that is automatically set in your controller which lets Authlogic know about the current controller object.

Then Authlogic leverages that to do everything, it's a pretty simple design. Nothing crazy going on, Authlogic is just leveraging the tools your framework provides in the controller object.

Under SemVer, changes to dependencies do not require a major release. Skip to content. Star 4. Permalink master. You should save your user objects this way as well, because you also want the user to verify that they own the OpenID identifier that they supplied. Notice we are saving with a block. Because we need to redirect the user to their OpenID provider so that they can authenticate.

When we do this, we don't want to execute that block of code, because if we do, we will get a DoubleRender error. This lets us skip that entire block and send the user along their way without any problems. If you are interested, I explain myself below. Regardless, if you don't feel comfortable with the organization of the logic,you can easily do this using the traditional method.

After the user has been authenticated just do this:. It's that simple. For more information there is a great OpenID tutorial at: railscasts. I agree with you on that comment, but my personal opinion is that these are not controller responsibilities.

It's all part of the authentication process, which is the entire purpose of this library. This library is not one big module of code, its a collection of modules that all deal with OpenID authentication. These modules get included wherever it makes sense.

That's the whole idea behind modules. To group common logic. Let's take a step back and look at the traditional method of OpenID authentication in rails. Git stats 52 commits. Failed to load latest commit information. View code. AuthlogicConnect Lists of known providers: Install 1.

Install AuthlogicConnect 2. Add the gem dependencies in your config: 3. Add the OpenIdAuthentication. Add the Migrations 5. Configure your keys 6. Make sure you save your objects properly 7. Flow Notes Todo. Install AuthlogicConnect sudo gem install authlogic-connect.

MIT License. Releases No releases published.