...
Identify the server URL or IP address that contains the solution you wish to integrate with. In this example, we may have a small solution a server called 'https://acme.com/' called 'AppBase Training' that we would like to interface with:
Our server URL would therefore be https://acme.com/Note title Server URL The above URL is an example only. Please use the URL of your actual server for these exercises.
- Confirm there is a valid account to be used for any web service calls available on the target tenant/server. In this example, on the https://acme.com server we have created a user account for web service calls (to manage security around which solutions can be accessed). The user login and password for this account is 'webapi':
Therefore the username and password for this user account - and what we will use to generate our security token for this example - is username: webapi and password: webapi
...
- Log into the tenant containing the solution (i.e. https://acme.com/) with your usual credentials or with credentials that gives you administrator access to the System Setup area of the tenancy:
- Click on System Setup Home > EnvironmentsSolutions. Click on the blue hyperlinked name of your solution:
- The domain code name can be found in the Domain field of Environment Details tab as below:
Therefore our domain name is AppBaseAPPBASE_TrainingTRAINING_QADEVELOPMENT.tenant1TENANT41
3 | Steps
- Our first call to the AppBase web service will be to retrieve a security token so that we can retrieve a token for subsequent web service calls. This involves sending a GET POST request to the AppBase Security Authentiation REST API that includes the credentials of the user. The full URL of the call will be:
https://acme.com/Security.WebService/AuthenticationServiceRest.svc/login?u=webapi&p=webapi
or
https://acme.com/Security.WebService/AuthenticationServiceRest.svc/loginJson
with json body:{
"Username": "webapi",
"Password": "webapi"
}
Or - The response you receive should be a long GUID that represents the security token that needs to be included in any subsequent call to the REST API:
Or