Authentication backwards compatibility

[claytondaley]

Legacy (v1) API endpoints do not support the access keys generated by the v2 authentication process. The Token authentication does not verify the token (yet) so it can be constructed with a v1 key. At the moment, however, a single BaseAPI instance cannot connect to both v1 and v2 resources.

Options include:

• Forcing the user to make separate v1 and v2 objects (current workaround)
• Dedicated v1 and v2 authentication providers
  • Both would need to be optional in the constructor which is NOT desirable
• A Chain of Responsibility (with some kind of NotSupportedError)

[claytondaley]

Asked FutureSimple if there is an easy way to connect to both and will await their response.

[claytondaley]

FutureSimple confirmed that you cannot access APIv1 endpoints using an OAuth2 token. Will be necessary to maintain separate v1 and v2 tokens presently.

[claytondaley]

Moved authentication modules into the v1 and v2 folders with custom logic. For now, the Base client will be dedicated to whichever type of authentication you feed it. #19 is the successor to this issue addressing the gaps in this resolution.