sensiolabs / connect
SymfonyConnect SDK
Fund package maintenance!
Tidelift
Installs: 25 847
Dependents: 1
Suggesters: 0
Security: 1
Stars: 90
Watchers: 18
Forks: 40
Open Issues: 0
Requires
- php: >=8.0.2
- ext-dom: *
- ext-json: *
- symfony/http-client: ^5.4|^6.0|^7.0
Requires (Dev)
- symfony/form: ^5.4|^6.0
- symfony/phpunit-bridge: ^5.4|^6.0|^7.0
- symfony/security-bundle: ^5.4|^6.0|^7.0
- dev-master / 8.x-dev
- v8.1.3
- v8.1.2
- v8.1.1
- v8.1.0
- v8.0.7
- v8.0.6
- v8.0.5
- v8.0.4
- v8.0.3
- v8.0.2
- v8.0.1
- v8.0.0
- v7.4.0
- v7.3.1
- v7.3.0
- v7.2.4
- v7.2.3
- v7.2.2
- v7.2.1
- v7.2.0
- v7.1.5
- v7.1.4
- v7.1.3
- v7.1.2
- v7.1.1
- v7.1.0
- v7.0.0
- v6.3.0
- v6.2.2
- v6.2.1
- v6.2.0
- v6.1.0
- v6.0.1
- v6.0.0
- 5.1.x-dev
- v5.1.6
- v5.1.5
- v5.1.4
- v5.1.3
- v5.1.2
- v5.1.1
- v5.1.0
- 5.0.x-dev
- v5.0.2
- v5.0.1
- v5.0.0
- 4.3.x-dev
- v4.3.4
- v4.3.3
- v4.3.2
- v4.3.1
- v4.3.0
- v4.2.3
- v4.2.2
- v4.2.1
- v4.2.0
- v4.1.0
- v4.0.0
- v3.0.0
- v2.1.0
- v2.0.2
- v2.0.1
- v2.0.0
- v1.9
- v1.8
- v1.7
- v1.6
- v1.5
- v1.4
- v1.3
- v1.2
- v1.1
- v1.0
- dev-fix-deprecation
- dev-exception-type
- dev-cleanup
This package is auto-updated.
Last update: 2024-06-06 14:49:55 UTC
README
About
This is the official SDK for the SymfonyConnect API. It works for the public API or with a registered OAuth application. To register an application, please go to your SymfonyConnect Account.
Installation
To install the SDK, run the command below and you will get the latest version:
composer require symfonycorp/connect
Usage
OAuth
To use the SDK in a Symfony application, we recommend using the built-in bundle.
Otherwise, you can take inspiration from the following part, which will show you how to include OAuth authentication within a Silex App.
Warning: We take for granted that you already have registered your app on
SymfonyConnect and that you're in
possession of your application_id
, application_secret
and scope
.
-
Configure your silex app with the data we gave us at app registration.
// index.php use SymfonyCorp\Connect\Api\Api; use SymfonyCorp\Connect\OAuthConsumer; $app = new Silex\Application(); $app['connect_id'] = 'application_id'; $app->register(new Silex\Provider\UrlGeneratorServiceProvider()); $app->register(new Silex\Provider\SessionServiceProvider()); $app['connect_secret'] = 'application_secret'; // List of scope copy-pasted from your application page on SymfonyConnect $app['connect_scope'] = array( 'SCOPE_ADDITIONAL_EMAILS', 'SCOPE_BIRTHDAY', 'SCOPE_EMAIL', 'SCOPE_LOCATION', 'SCOPE_PUBLIC', 'SCOPE_SSH_KEYS', ); $app['connect_consumer'] = new OAuthConsumer( $app['connect_id'], $app['connect_secret'], implode(' ', $app['connect_scope']) // scope MUST be space separated ); $app['connect_api'] = new Api();
This done. We can now move on to the second step.
-
We need to create two controllers to handle the OAuth2 Three-Legged workflow.
The first controller goal is to redirect the user to SymfonyConnect in order to ask him for the authorization that your app will use his data. This controller will be bound to the
connect_auth
route. In your template, you'll need to create a link to this route.// index.php $app->get('/connect/new', function () use ($app) { $callback = $app['url_generator']->generate('connect_callback', array(), true); $url = $app['connect_consumer']->getAuthorizationUri($callback); return $app->redirect($url); })->bind('connect_auth');
The second controller is the one that will welcome the user after SymfonyConnect redirected him to your application. When registering your client, you'll have to provide the exact absolute URL that points to this controller.
$app->get('/connect/callback', function (Request $request) use ($app) { // There was an error during the workflow. if ($request->get('error')) { throw new \RuntimeException($request->get('error_description')); } // Everything went fine, you can now request an access token. try { $data = $app['connect_consumer']->requestAccessToken($app['url_generator']->generate('connect_callback', array(), true), $request->get('code')); } catch (OAuthException $e) { throw $e; } // At this point, we have an access token and we can use the SDK to request the API $app['connect_api']->setAccessToken($data['access_token']); // All further request will be done with this access token $root = $app['connect_api']->getRoot(); $user = $root->getCurrentUser(); $user->getBadges()->refresh(); $app['session']->start(); $app['session']->set('connect_access_token', $data['access_token']); $app['session']->set('connect_user', $user); return $app->redirect('/'); })->bind('connect_callback');
-
Create a link from your template
In a template, you can use the following snippet of code to render a SymfonyConnect button:
<a href="#" class="connect-with-symfony"> <span>Log in with SymfonyConnect</span> </a>
And include the following CSS file:
https://connect.symfony.com/css/sln.css
Et voilà! Your application can now use SymfonyConnect as an authentication method!
The API
The SymfonyConnect Connect API is RESTFul and (tries to) conforms to the HATEOAS principle.
Here are some useful recipes.
-
Search
$root = $api->getRoot(); // Will search for users $users = $root->getUsers('fab');
-
Edit authenticated user
$app['connect_api']->setAccessToken($app['session']->get('connect_access_token')); $root = $app['connect_api']->getRoot(); $user = $root->getCurrentUser(); $user->setBiography("I'm sexy and I know it."); $user->submitForm();
As you can see by these examples, you always have to to go through the API Root to make an action. This is because the API is discoverable and that the SDK should not know anything beside the API's entry point.
License
This library is licensed under the MIT license.