This package provides Salla OAuth 2.0 support for the PHP language OAuth 2.0 Client.
Explore our blogs »
Report Bug ·
Request Feature
· </Salla Developers>
To use this package, it will be necessary to have a Salla client ID and client secret. These are referred to as {client-id} and {client-secret} in the documentation.
Please follow the Salla instructions to create the required credentials.
You can install the package via Composer:
composer require salla/ouath2-merchant<?php
require_once './vendor/autoload.php';
use Salla\OAuth2\Client\Provider\Salla;
$provider = new Salla([
'clientId' => '{client-id}', // The client ID assigned to you by Salla
'clientSecret' => '{client-secret}', // The client password assigned to you by Salla
'redirectUrl' => 'https://yourservice.com/callback_url', // the url for current page in your service
]);
/**
* In case the current callback url doesn't have an authorization_code
* Let's redirect the merchant to the installation/authorization app workflow
*/
if (empty($_GET['code'])) {
$authUrl = $provider->getAuthorizationUrl([
'scope' => 'offline_access',
//Important: If you want to generate the refresh token, set this value as offline_access
]);
header('Location: '.$authUrl);
exit;
}
/**
* The merchant completes the installation/authorization app workflow
* And the callback url has an authorization_code as a parameter
* Let's exchange the authorization_code with access token
*/
try {
$token = $provider->getAccessToken('authorization_code', [
'code' => $_GET['code']
]);
//
// ## Access Token
//
// You should store the access token
// which may use in authenticated requests against the Salla's API
echo 'Access Token: '.$token->getToken()."<br>";
//
// ## Refresh Token
//
// You should store the refresh token somewhere in your system because the access token expired after 14 days,
// so you can use the refresh token after that to generate a new access token without asking any access from the merchant
//
// $token = $provider->getAccessToken(new RefreshToken(), ['refresh_token' => $token->getRefreshToken()]);
//
echo 'Refresh Token: '.$token->getRefreshToken()."<br>";
//
// ## Expire date
//
// This helps you to know when the access token will be expired
// so before that date, you should generate a new access token using the refresh token
echo 'Expire Date : '.$token->getExpires()."<br>";
//
// ## Merchant Details
//
// Using the access token, we may look up details about the merchant.
// --- Same request in Curl ---
// curl --request GET --url 'https://accounts.salla.sa/oauth2/user/info' --header 'Authorization: Bearer <access-token>'
/** @var \Salla\OAuth2\Client\Provider\SallaUser $user */
$user = $provider->getResourceOwner($token);
/**
* {
* "id": 1771165749,
* "name": "Test User",
* "email": "[email protected]",
* "mobile": "+966500000000",
* "role": "user",
* "created_at": "2021-12-31 11:36:57",
* "merchant": {
* "id": 1803665367,
* "username": "dev-j8gtzhp59w3irgsw",
* "name": "dev-j8gtzhp59w3irgsw",
* "avatar": "https://i.ibb.co/jyqRQfQ/avatar-male.webp",
* "store_location": "26.989000873354787,49. 62477639657287",
* "plan": "special",
* "status": "active",
* "domain": "https://salla.sa/YOUR-DOMAIN-NAME",
* "created_at": "2021-12-31 11:36:57"
* }
* }
*/
var_export($user->toArray());
echo 'User ID: '.$user->getId()."<br>";
echo 'User Name: '.$user->getName()."<br>";
echo 'Store ID: '.$user->getStoreID()."<br>";
echo 'Store Name: '.$user->getStoreName()."<br>";
//
// 🥳
//
// You can now save the access token and refresh the token in your database
// with the merchant details and redirect him again to Salla dashboard (https://s.salla.sa/apps)
//
// ## Access to authenticated APIs for the merchant
//
// You can also use the same package to call any authenticated APIs for the merchant
// Using the access token, information can be obtained from a list of endpoints.
//
// --- Same request in Curl ---
// curl --request GET --url 'https://api.salla.dev/admin/v2/orders' --header 'Authorization: Bearer <access-token>'
$response = $provider->fetchResource(
'GET',
'https://api.salla.dev/admin/v2/orders',
$token->getToken()
);
var_export($response);
} catch (\League\OAuth2\Client\Provider\Exception\IdentityProviderException $e) {
// Failed to get the access token or merchant details.
// show an error message to the merchant with good UI
exit($e->getMessage());
}Refresh tokens are only provided to applications that request offline access. You can specify offline access by passing the scope option in your getAuthorizationUrl() request.
use Salla\OAuth2\Client\Provider\Salla;
$provider = new Salla([
'clientId' => '{client-id}',
'clientSecret' => '{client-secret}',
]);
$refreshToken = 'FromYourStoredData';
$token = $provider->getAccessToken('refresh_token', ['refresh_token' => $refreshToken]);You can seamlessly integrate Salla OAuth2 within Laravel using the facade helper provided by the package. Here's how you can do it:
First, use the facade helper in your Laravel project:
use \Salla\OAuth2\Client\Facade\SallaOauth;
// Generate the authorization URL with the required scope
$authUrl = SallaOauth::getAuthorizationUrl([
'scope' => 'offline_access',
// Important: Set this value to 'offline_access' to generate a refresh token
]);
// Retrieve the access token using the authorization code
$token = SallaOauth::getAccessToken('authorization_code', [
'code' => request()->get('code')
]);To configure the OAuth2 service, set the necessary environment variables in your .env file:
SALLA_OAUTH_CLIENT_ID=""
SALLA_OAUTH_CLIENT_SECRET=""
SALLA_OAUTH_CLIENT_REDIRECT_URI=""These settings ensure that your Laravel application can properly communicate with the Salla OAuth2 service, allowing you to handle authentication and retrieve access tokens efficiently.
When integrating Salla OAuth2 for authentication, you may need to validate the merchant's access token and retrieve user information during a request.
To achieve this, add the \Salla\OAuth2\Client\Http\OauthMiddleware middleware to the routes you wish to protect. This middleware ensures that a user is logged in via Salla OAuth2.
However, note that this middleware only verifies user authentication. Additional authorization checks must be implemented separately as needed. The package conveniently stores the resource owner information as a request attribute, facilitating further authorization.
After adding the middleware to your route, you can access the current authenticated user using the following code:
auth()->guard('salla-oauth');
// To check if a user is authenticated:
auth()->guard('salla-oauth')->check();
// To get the authenticated user's ID:
auth()->guard('salla-oauth')->id();
// To get the merchant information of the authenticated user:
auth()->guard('salla-oauth')->merchant();By leveraging this middleware, you ensure secure access to your routes while maintaining flexibility for additional authorization requirements.
composer testThe team is always here to help you. Happen to face an issue? Want to report a bug? You can submit one here on GitHub using the Issue Tracker. If you still have any questions, please contact us by joining the Global Developer Community on Telegram or via the Support Email.
Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
If you discover any securitys-related issues, please email [email protected] instead of using the issue tracker.
The MIT License (MIT). Please see License File for more information.