While it is tempting to simply “hard code” the application to point to a particular server, such as my20.geotab.com, this is the incorrect approach. Over the course of time a database is not guaranteed to remain on the same server. It is common for load balancing to occur and resources to be transferred from one server to another as necessary. To prevent the application from losing its connection to the correct database, authentication calls must be made to the root federation server instead of making the request to a particular server.
As an example; making an authentication call to “my.geotab.com” and authentication occurring. Such a call could be made as:
Where the database, user and password are set by you.
If however if a Session ID is require, it can be retrieved by
- Log in to the MyGeotab database using your credentials
- Open up Developer Tools within the browser (F12 shortcut on the keyboard)
- Click Network
- If this section is empty, refresh the page to reload the data
- Click on any of the apiv1 files within the Name panel
- Within the Headers tab, scroll down to the Form Data section
- Within the JSON object listed in JSON-RPC, find the part of the JSON which lists "credentials"
- The current session ID is listed in the "credentials" object