If you are developing your own plugin for your Staffbase app we describe the authentication flow of a plugin at https://developers.staffbase.com/guide/customplugin-overview/. While this documentation just covers the conceptual ideas of the interface of plugins though – the so called Plugin SSO – we want to provide a library to help you develop your first plugin for Staffbase even faster. This SDK provides the basic functionality to parse and verify a provided token for PHP.
We provide our Plugin SDK via Composer (https://packagist.org/packages/staffbase/plugins-sdk-php). Thus, you can just use Composer for installation:
composer require staffbase/plugins-sdk-php
Dependencies are also managed by Composer. When using this repository keep the following dependencies in mind (cf. composer.json):
- php: ^7.4.0 || ^8.0
- lcobucci/jwt: ^4.1
For the API reference of this SDK please consult the docs.
You can try to create a token from the received jwt.
use Exception;
use Staffbase\plugins\sdk\SSOToken;
try {
$appSecret = 'abcdef012345='; // the public key received from Staffbase.
$sso = new SSOToken($appSecret, $_GET['jwt']);
print "Hello again ". $sso->getFullName();
} catch (Exception $e) {
print "Sorry we could not authenticate You.";
exit;
}To manage multiple instances easy and secure we provide a convenience class which abstracts the session.
The PluginSession class has the same data interface as SSOToken. It also provides the means to set a custom session save handler as the optional third parameter of __construct. PluginSession will automatically take care of reading the URL parameters and saving the SSO info in the session for further requests after the Token gets invalid.
use Exception;
use Staffbase\plugins\sdk\PluginSession;
try {
$pluginId = 'weatherplugin'; // the id you received from Staffbase.
$appSecret = 'abcdef012345='; // the public key received from Staffbase.
$session = new PluginSession($pluginId, $appSecret);
print "Hello again ". $PluginSession->getFullName(). ', '. $PluginSession->getSessionVar('message');
} catch (Exception $e) {
print "Sorry we could not authenticate You.";
exit;
}With the version 1.2.0 we introduced the concept of remote calls. These can happen if the Staffbase app need's to notify the plugin about an event which may be relevant. Events could be such as: a plugin instance gets deleted or a user should be logged out. For now we support only the instance-deletion call. You can find all supported calls in the RemoteCall namespace.
use Staffbase\plugins\sdk\RemoteCall\AbstractRemoteCallHandler;
use Staffbase\plugins\sdk\RemoteCall\DeleteInstanceCallHandlerInterface;
// create a call handler which can have multiple call interfaces implemented
class RemoteCallHandler extends AbstractRemoteCallHandler implements DeleteInstanceCallHandlerInterface {
private $db;
public function __construct($db) {
$this->db = $db;
}
public function deleteInstance($instanceId) {
$result = $this->db->posts->deleteByInstance($instanceId);
return $result !== false;
}
}
// pass it to the PluginSession on construction as the last parameter
$remoteCallHandler = new RemoteCallHandler($db);
$session = new PluginSession(PLUGIN_ID, $secret, $sessionHandler, null, $remoteCallHandler);
/* Unreachable code in a delete call follows */
...Please notice that a remote call will either be exited through proper implementation of RemoteCallInterface's exit functions or forcefully with a warning. This happens because practically there is no session to built after a call.
- Fork it
- Create a branch
git checkout -b feature-description - Put your name into authors.txt
- Commit your changes
git commit -am "Added ...." - Push to the branch
git push origin feature-description - Open a Pull Request
To run the tests a simple # composer test command in the root directory will suffice. Please consult composer.json to learn which phpunit version is currently in use.
Copyright 2017-2022 Staffbase GmbH.
Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0