SPIKE - Investigate implementing OAuth Authentication for the Day Track Report

As a developer I want to research how to implement OAUTH authentication in to the Day Track Report so that when we call the Labor Cost v4 endpoint, it works!

Notes from CFA

• Here is the URL for the daily view of labor cost: https://real-time.labor.restaurant.api-test.cfadevelop.com/v4/cost?locationNum=30001&businessDate=2020-10-06&useAverageWageRate=false . This endpoint will return costs at the 15 minute interval like v3.
• There is also an endpoint that gives a monthly view, but it only has daily totals - no 15 minute intervals. It can be accessed here: https://real-time.labor.restaurant.api-test.cfadevelop.com/v4/monthlyCost?locationNum=02206&year=2020&month=10&useAverageWageRate=false.

• As for authentication, this endpoint is authenticated only by Okta token. If HotSchedules does not already have a client set up, then Brent Bucker can help with that. Documentation on using Okta can be found here. At a high level Okta authentication is done in a multistep process:
• Brent Bucker creates a client ID and secret that are given to HotSchedules. Think of this like a username and password
• HotSchedules reaches out to Okta for a token using basic auth and the client ID and secret from above. They will receive a token that is good for a certain amount of time (I forget, exactly but maybe an hour?)
• HotSchedules will hit v4 passing in the token using the "Bearer Token" header. They can make as many requests with the same token as long as that token has not expired.

In addition to looking at Authentication, it would be good to look at the options for pulling back data, by day vs by 15 minute intervals.

• I have no idea how we pull this data today, but it seems that we could use whole days for dates before today, and then just hit the 15 minute endpoint for data for today