Download the PHP package maras0830/laravel5-battlenet-api without Composer
On this page you can find all versions of the php package maras0830/laravel5-battlenet-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package laravel5-battlenet-api
Laravel5-BattleNet-API =========================== The Battle.net API uses OAuth 2.0, a federated access control mechanism, to help secure sections of the APIs that we provide out to the public. By using OAuth, you can let Battle.net handle the authentication process and receive a unique ID representing that user, then use an access token to gain access to allowed resources like their World of Warcraft characters, StarCraft II profile, or other data as appropriate. The usage of OAuth itself is relatively simple, but the flows can seem a little intimidating at first. Hopefully, by following the processes below, you can quickly integrate with Battle.net and worry more about building that cool idea and less about how to get data from players.
BattleNet oAuth just provide simple account information(battlenet account id, battlenet tag), Like this:
*Just support oauth and get authenticated user, and I will develop WOW and SC2 Game Data API in the future and welcome evenyone if you also love laravel and Blizzard join.
See official Github Blizzard Github See official API Document Battle.Net Developer
Installation
將 package 加入
Require the package in composer.json :
在 ``config/app.phpconfig/app.phpprovidersconfig/app.phpaliasesconfig/battlenet-api.php``` ,並且根據 Battle.Net Developer 進行註冊與開發者配置 you will find config file after published, register abd set up by Battle.Net Developer
USAGE
you can use authenticationURL on routes and controller, like this:
routes:
And callback function:
OAuth 2.0
OAuth 2.0 is the next evolution of the OAuth protocol which was originally created in late 2006. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. This specification is being developed within the IETF OAuth WG and is based on the OAuth WRAP proposal.
HTTPS
One of the major changes to OAuth when releasing version 2.0 was removing transport considerations from the protocol, instead relying on implementors to handle the transport of codes and tokens themselves. What this means in practical terms is that HTTPS is required, and for extra security, checking the cert during the HTTPS handshake is recommended. This will prevent any surprises and will prevent the codes from being captured while in transit.