Authentication

(Difference between revisions)
Jump to: navigation, search
(How to get Wi-Fi API id/secret pair?)
Line 1: Line 1:
All Social-ID NOW Restful APIs make use of HTTP Basic for authentication.
+
All CoffeeBean Restful APIs make use of HTTP Basic for authentication.
  
Most APIs require authentication through the id/secret pair of a Marketing Account or a Social Login App.  
+
Most APIs require authentication through the id/secret pair of an Account or a Login App.  
  
However, some APIs may be used without any authentication. An example is the login/info API, which only requires the Social Login App secret that can be found in the Social Login App settings.
+
However, some APIs may be used without any authentication. An example is the login/info API, which only requires the Login App secret that can be found in the Social Login App settings.
  
= Marketing Account Authentication =
+
= Account Authentication =
  
Each Marketing Account has its own id/secret pair to access available APIs.
+
Each Account has its own id/secret pair to access available APIs.
  
 
<b>This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).</b>
 
<b>This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).</b>
  
== How to get Marketing Account id/secret pair? ==
+
== How to get Account id/secret pair? ==
  
Once you log into the Social-ID Now platform and set up a Marketing Account, access keys can be found in the following URL:
+
Once you log into the CoffeeBean Identity and Access Platform and set up an Account, access keys can be found in the following URL:
  
 
   https://app.socialidnow.com/marketing/apis
 
   https://app.socialidnow.com/marketing/apis
Line 21: Line 21:
 
   curl --user <api_id>:<api_secret> <nowiki>https://api.socialidnow.com/<path></nowiki>
 
   curl --user <api_id>:<api_secret> <nowiki>https://api.socialidnow.com/<path></nowiki>
  
= Social Login App Authentication =
+
= Login App Authentication =
  
Each Social Login App has its own id/secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Social Login App used for authentication.
+
Each Login App has its own id/secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Login App used for authentication.
  
 
<b>This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).</b>
 
<b>This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).</b>
  
== How to get Social Login App id/secret pair? ==
+
== How to get Login App id/secret pair? ==
  
Each Social Login App has an API area where access keys can be found:
+
Each Login App has an API area where access keys can be found:
  
 
  [https://app.socialidnow.com/marketing/login/apps/login_app_id/apis https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis]
 
  [https://app.socialidnow.com/marketing/login/apps/login_app_id/apis https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis]
Line 39: Line 39:
 
   curl --user <login_app_id>:<api_secret> <nowiki>https://api.socialidnow.com/<path></nowiki>
 
   curl --user <login_app_id>:<api_secret> <nowiki>https://api.socialidnow.com/<path></nowiki>
  
= Social Login App Client Authentication =
+
= Login App Client Authentication =
  
Each Social Login App has its own id/client secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Social Login App used for authentication.
+
Each Login App has its own id/client secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Login App used for authentication.
  
 
<b>This authentication may be used on server applications (backend) or client applications (frontend/mobile).</b>
 
<b>This authentication may be used on server applications (backend) or client applications (frontend/mobile).</b>
  
== How to get Social Login App id/client secret pair? ==
+
== How to get Login App id/client secret pair? ==
  
Each Social Login App has an API area where access keys can be found:
+
Each Login App has an API area where access keys can be found:
  
 
  [https://app.socialidnow.com/marketing/login/apps/login_app_id/apis https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis]
 
  [https://app.socialidnow.com/marketing/login/apps/login_app_id/apis https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis]
Line 65: Line 65:
 
== How to get Wi-Fi API id/secret pair? ==
 
== How to get Wi-Fi API id/secret pair? ==
  
Once you log into the Social-ID Wi-Fi platform and set up your account, API credentials can be found in the following URL:
+
Once you log into the CoffeeBean Wi-Fi platform and set up your account, API credentials can be found in the following URL:
  
 
   https://wifi.socialidnow.com/admin/account/edit
 
   https://wifi.socialidnow.com/admin/account/edit

Revision as of 14:34, 10 May 2019

All CoffeeBean Restful APIs make use of HTTP Basic for authentication.

Most APIs require authentication through the id/secret pair of an Account or a Login App.

However, some APIs may be used without any authentication. An example is the login/info API, which only requires the Login App secret that can be found in the Social Login App settings.

Contents

Account Authentication

Each Account has its own id/secret pair to access available APIs.

This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).

How to get Account id/secret pair?

Once you log into the CoffeeBean Identity and Access Platform and set up an Account, access keys can be found in the following URL:

  https://app.socialidnow.com/marketing/apis

Example

  curl --user <api_id>:<api_secret> https://api.socialidnow.com/<path>

Login App Authentication

Each Login App has its own id/secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Login App used for authentication.

This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).

How to get Login App id/secret pair?

Each Login App has an API area where access keys can be found:

https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis

The App id is in the url (<login_app_id>). The App secret is the "API secret" key.

Example

  curl --user <login_app_id>:<api_secret> https://api.socialidnow.com/<path>

Login App Client Authentication

Each Login App has its own id/client secret pair to access available APIs. In those APIs the information created or retrieved will always be associated with the Login App used for authentication.

This authentication may be used on server applications (backend) or client applications (frontend/mobile).

How to get Login App id/client secret pair?

Each Login App has an API area where access keys can be found:

https://app.socialidnow.com/marketing/login/apps/<login_app_id>/apis

The App id is in the url (<login_app_id>). The App client secret is the "API client secret" key.

Example

  curl --user <login_app_id>:<api_client_secret> https://api.socialidnow.com/<path>

Wi-Fi API Authentication

Each Wi-Fi Account has its own id/secret pair to access available APIs.

This authentication must be used only on server applications (backend), never on client applications (frontend/mobile).

How to get Wi-Fi API id/secret pair?

Once you log into the CoffeeBean Wi-Fi platform and set up your account, API credentials can be found in the following URL:

  https://wifi.socialidnow.com/admin/account/edit

Example

  curl --user <wifi_api_id>:<wifi_api_secret> https://wifi.socialidnow.com/<path>
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox