Local Server
A local server is an application (server) that can be used by wallet users to access certain GCP services such as initiate payment, view card/wallet details, etc. Local server represents each system that integrates and consumes GCP APIs.
Local server examples:
TH Wallet Local Server: Represents the local service system that integrates with GCP and serves the TH Wallet application.
PH Wallet Local Server: Represents the local service system that integrates with GCP and serves the PH Wallet application.
Significance of a Local Server
The local server can access some of these services without user intervention (such as initiate payment, view card / wallet details, etc.)
Many services can only be accessed with tokens that are generated with local server and user details (such as edit profile, edit card/wallet details, etc.)
A local server is not necessarily needed for a tenant (a tenant may exist without a local server), but a local server needs to be associated with a tenant (a local server cannot exist without a tenant)
As an admin you can create and update local servers from the admin panel. From the 'GCP Settings' sidebar click on 'Local Server'. This will bring about the list of all local servers with their details. The list can be sorted in both ascending and descending order of information such as Local Server Name, Country code, Client ID, BackOffice URL and Redirect URL. The local server list will help keep track of all the local servers that have been created and all the information related to each local server.
All the local server can be seen from the list of all local servers. You can click on a local server in order to view all details of that specific local sever. Information of a specific local server contains:
UID
String
Use for verify on the registration or sign-in page
Local server name
String
Name of the local server
Secret Key
String
Use as secret for getting local server token
Tenant
String
Name of the assigned tenant
Country code
String
For example - TH, PH
BackOffice URL
String
URL of the BackOffice
Redirect URL
String
Use for verify on the registration and sign-in page and the URL for the user to be redirected to after registered or signed-in
You can click on the local server in the list to go directly to the local server detail page. In the local server detail page, you can see more information of the local server (Name, Client ID [UID], Description, Secret, Redirect URLs, Tenants).
Additionally, this page will also contain details about:
The custom interval period set for the Wallet User and Office User refresh tokens.
Custom/configured value of absolute TTL for the refresh token.
The custom time period set for the phone number to be blocked from re-registration by the user.
However, these fields are not editable by the Super admin user. They can be customised and set up by the Tenant admin user only.
Last updated