Updating API partner credentials

FareHarbor requires some of our partners to use a “Basic Auth” username/password pair when making API requests to FareHarbor servers (this is one of the oldest password challenge protocols on the Internet).

This Basic Auth authentication comes before doing anything else. Note that there may be additional security measures in place downstream of this.

Reserve with Google

Reserve with Google requires that we change the Basic Auth password at least once every 180 days. The credentials can be found here.

Reserve with Google will send several emails as the expiry date approaches.

Website Travel

TBD (can’t log in to their dashboard ATM)

How to create API partner credentials on the FareHarbor website

On our side, the username/password pair are managed as a Channel App in the Integrations section of the Dashboard.

The Channel App “SKU” corresponds to the Basic Auth username, and the “Key” corresponds to the password.

Note: There can be more than one Channel App with the same “SKU”. If there is more than one, then any of the “Key”s corresponding to the “SKU” are acceptable passwords for the Basic Auth. This is an important detail because it allows us to rotate keys in a graceful manner without changing the username.

Password rotation sequence

The sequence looks like this:

1. From here, click Add Channel App. The SKU will be the username for Basic Auth. In the case of Reserve with Google, “ReserveWithGoogle” is the SKU/username. In the case of Website Travel, it is “WebsiteTravel”. The Name can be anything reasonable and informative (for example, it could include the date of creation, if desired). The Key is generated automatically.
2. On the partner dashboard, the Username should not normally need to be changed. On the partner dashboard, the Password should be changed to the new Key just created in the Channel App.
3. Once we confirm that things are working as expected (by waiting 24 hours and verifying that there are no unexpected errors), the old Channel App may be deleted (this is where it may be useful to have dates in the names of the Channel Apps, to distinguish the old from the new).