Download the PHP package ekoapp/eko-oauth-sdk without Composer

On this page you can find all versions of the php package ekoapp/eko-oauth-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of ekoapp/eko-oauth-sdk

Informations about the package eko-oauth-sdk

EkoOAuthSDK-PHP

An OAuth authentication client for integrating 3rd party application with Eko App.

Prerequisites

Client application must be registered with Eko first. These values, redirect_uri, client_id, client_secret and eko_uri, will be defined during registration process.

Running Example

  1. Edit the client_id, client_secret, redirect_uri and eko_uri in /examples/app.php.
  2. Go to http://localhost/path/to/project/examples/app.php via the browser

Installation

Usage

See examples/app.php for the complete flow of usage.

1. Initialization

2. Authentication

To authenticate a user, the client application must redirect the user to the url below.

3. Get token and user info

The client application must setup an endpoint which must match the predefined redirect_uri. After authentication success or fail, Eko will redirect the user back to this redirect_uri endpoint along with state and code (authentication code) as query parameters. The client application must validate the incoming state with the one previously store on the session. Then, the client application use the code to retrieve access token and use the access token to retrieve user info. DO NOT use the code if state validation fail.

or a shortcut to retreive user info ...

4. Refresh Token

Release

Version Changes
1.0.0
  • Initial release

Authors

All versions of eko-oauth-sdk with dependencies

PHP Build Version
Package Version
Requires rmccue/requests Version ^1.7
firebase/php-jwt Version ^5.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ekoapp/eko-oauth-sdk contains the following files

Loading the files please wait ....