Download the PHP package stellarsecurity/stellarsecurity-vpn-laravel without Composer
On this page you can find all versions of the php package stellarsecurity/stellarsecurity-vpn-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download stellarsecurity/stellarsecurity-vpn-laravel
More information about stellarsecurity/stellarsecurity-vpn-laravel
Files in stellarsecurity/stellarsecurity-vpn-laravel
Package stellarsecurity-vpn-laravel
Short Description Enterprise SDK for Stellar VPN integration.
License proprietary
Informations about the package stellarsecurity-vpn-laravel
StellarSecurity Laravel VPN SDK
This package provides a Laravel-friendly SDK for integrating with the Stellar VPN backend from any Stellar UI API service.
Installation
Add the package to your project (after publishing it to your chosen package registry):
If you are not using Laravel package auto-discovery, register the service provider manually in config/app.php:
Configuration
Publish the configuration file:
This will create config/stellar_vpn.php.
Environment variables used:
Note: Set the username and password to the Basic Auth credentials used by the Stellar VPN API.
Available Methods
All core operations are exposed through StellarSecurity\LaravelVpn\Services\VpnServerClient.
You can type-hint it in your controllers or services and let Laravel inject it:
1. List VPN Servers
- Calls:
GET /v1/vpnservercontroller/list - Returns:
arrayof server entries, e.g.:
2. Issue or Fetch VPN Credentials
- Calls:
POST /v1/vpncredentialcontroller/credentials -
Body:
- Returns a response array from the API, typically:
3. Revoke Credentials for a Single Device
- Calls:
POST /v1/vpncredentialcontroller/reset - Returns:
trueifresponse_code === 200, otherwisefalse.
4. Revoke ALL Credentials for a User
- Calls:
POST /v1/vpncredentialcontroller/reset-all - Returns:
trueifresponse_code === 200, otherwisefalse.
Example Controller
Notes
- All calls use HTTP Basic Auth against the Stellar VPN API.
- Errors from the remote API should be handled at the UI API level (e.g. logging, retries, custom HTTP responses).