Libraries tagged by required
dinh0012/generators
30 Downloads
This package will generate a Laravel Model based on your database table itself, filling in the required fields automatically.
diglin/sylius-advanced-api
7 Downloads
Add additional information required to make the OroCRM integration working. Can be used for other purposes
diglin/oro-deepl
615 Downloads
Allow to extract non translated strings from OroPlatform applications and translate them through deepl web service. A Deepl developer account is required
devcake/hotspotpackage
79 Downloads
Package that contains all models and migrations required to support hotspots in our VR backends
depage/mail
96 Downloads
depage-mail is a small simple mail generator and sender and a more convinient wrapper for the mail() function, when something bigger is unnecessary or not required.
denisgold/core-module
9 Downloads
The core module for AsgardCMS. This is required for every install by Denis Stoliarchuk.
dd/evolutioncms-snippets-ddsendfeedback
1 Downloads
A snippet for sending users' feedback messages to a required email, slack and telegram chats or SMS through sms.ru. It is very useful along with ajax technology.
dd/evolutioncms-snippets-ddif
1 Downloads
This snippet compares different values and returns required chunk or string.
dd/evolutioncms-snippets-ddgetparentid
0 Downloads
Gets document parent ID(s) of the required level.
dd/evolutioncms-plugins-managermanager-mm_synch_fields
0 Downloads
Widget for ManagerManager plugin that allows a few fields values to be synchronized while editing the document. E. g. it`s required that page title and menu title have the same value. It's especially useful when some values being synchronized are hidden.
dd/evolutioncms-plugins-managermanager-mm_requirefields
0 Downloads
A widget for ManagerManager plugin that allows document fields (or TVs) to become required.
dd/evolutioncms-plugins-ddsendredirect
0 Downloads
Redirects from required non-existent URLs to required target URLs.
dbosen/license-check
1 Downloads
License checker for required packages.
dasundev/nova-access-secret
351 Downloads
Secure your Laravel Nova access with a required secret key in the URL.
daphascomp/daphascompsms
1 Downloads
# Authentication Requests made to our APIs must be authenticated, there are two ways to do this: 1. Authenticating using your API apiUsername and apiPassword - `Basic Auth` 2. Authenticating using an Auth Token - `Bearer Token` ## Method 1: Basic Auth Basic Authentication is a method for an HTTP user agent (e.g., a web browser) to provide a apiUsername and apiPassword when making a request. When employing Basic Authentication, users include an encoded string in the Authorization header of each request they make. The string is used by the request’s recipient to verify users’ identity and rights to access a resource. The Authorization header follows this format: > Authorization: Basic base64(apiUsername:apiPassword) So if your apiUsername and apiPassword are `onfon` and `!@pas123`, the combination is `onfon:!@pas123`, and when base64 encoded, this becomes `b25mb246IUBwYXMxMjM=`. So requests made by this user would be sent with the following header: > Authorization: Basic b25mb246IUBwYXMxMjM= | Description | | ---------------------------------------------------------------------------------------------- | | **apiUsername** `String` `Required` Your onfon account apiUsername, retrieved from portal | | **apiPassword** `String` `Required` Your onfon account apiPassword, retrieved from portal | ## Method 2: Bearer Tokens This authentication stategy allows you to authenticate using JSON Web Token ``JWT` that will expire after given duration. Each Access Token is a `JWT`, an encoded JSON object with three parts: the `header`, the `payload`, and the `signature`. The following is an example Access Token generated for Conversations > Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c ### Getting the token To generate the token, make a `POST` request to `/v1/authorization` endpoint with your `apiUsername` and `apiPassword` This request should be made from your server and not on the client side such as browser or mobile environment. You will receive a JSON similar to below: `{ "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c", "validDurationSeconds": 3600}` You can use the token received to make API calls. The token will be valid for value of `validDurationSeconds`, before which you should generate a new token. #### Request Body ``` { "apiUsername": "root", "apiPassword": "hakty11" } ``` #### Response Body ``` { "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c", "validDurationSeconds": 3600 } ``` #### Example Curl ``` curl --location --request POST 'https://apis.onfonmedia.co.ke/v1/authorization' \ --data-raw '{ "apiUsername": "correctapiUsername", "apiPassword": "correctapiPassword" } ``` #### Making an API call You will be required to pass the token in `Authorization` header prefixed by `Bearer` when calling other endpoints. Example `Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c`