Opauth Plugin for PHP Fat-Free Framework

v1.0.1 2019-05-02 07:00 UTC

This package is auto-updated.

Last update: 2022-06-06 01:16:48 UTC


This is a plugin for easy integration of Opauth for PHP Fat-Free Framework.


  • A: use composer composer require ikkez/f3-opauth
  • or B: put the opauth folder somewhere into your libs or autoloaded directory, and adjust the autoload path:
// adjust the autoloader


  1. You need to configure each strategy you want to use on your service. You can find instructions how to do that in each strategy folder's readme file. Basically you only need to create some OAuth consumer apps on the strategy's provider and add the key/secret credentials to the config file. Google,Facebook,Twitter,and Github are already included here, so you can skip the Install part in their readme files. If you need more OAuth providers, check the the list of strategies.
  2. This plugin comes with its own configuration file. It's used to provide all strategy configuration to Opauth, as well as some F3 routing settings. You should at least change the security_salt and your favorite strategy keys and secrets.
  3. Integrate the authorization into your existing login procedure.

Basic Usage

// in your index.php
$f3 = \Base::instance();
// load opauth config (allow token resolve)
$f3->config('lib/opauth/opauth.ini', TRUE);

// init with config
$opauth = OpauthBridge::instance($f3->opauth);

// define login handler
	header('Content-Type: text');
	echo 'User successfully authenticated.'."\n";

// define error handler
	header('Content-Type: text');
	echo 'Auth request was canceled.'."\n";


The event handlers can also be callable string:


To login, call a strategy, i.e.http://domain.com/auth/facebook.

Application flow

  1. Alright, you place a social login button near your regular login form, that send the user to the login strategy, i.e. http://domain.com/auth/facebook.
  2. When a user authenticated to a provider, the user is send back to a callback-route. The callback checks if the request and auth was valid. Then, when the authorization was successful, the onSuccess handler is called and provides you some data from the given strategy.
  3. You can use this data to extract a username, access-token, email or what ever suits best for that strategy. Each strategy provides different data, so depending on your application needs, you perhaps should consider to add some fallback mechanisms into your application (i.e. it can happen that you wont get an email from twitter or facebook). You can use this data to find a match in your user database. Depending on the result you can start your login or registration controller.
  4. On registration, you might want to save that unique-something from the strategy-auth-data to the user table (email, or $f3->hash on multiple fields like username,token,id) - this way you know who has activated a social auth provider and get the chance to load the user based on this.
  5. After registration and on login, you probably save an active user session in your controller to memorize your logged in user.
  6. When the session is expired or the user need to login again from another device, send him to the auth strategy route again (auth/facebook - instant redirect after successful activation on most providers), and now you can find him in your user table with activated social auth and login him in directly.

This is of course just one idea of implementation. Some providers also return tokens for further communication with their 3rd party API (i.e. to fetch more profile data or renew tokens), but that's something this plugin is not going to handle. Have a look at the strategy docs for more information.