Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-12458

SPIKE - Investigate implementing OAuth Authentication for the Day Track Report

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Won't Develop
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • SCRUM Team:
      Brotherhood of Mutants
    • Work Type Classification:
      Sustaining

      Description

      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

      • 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

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              • Assignee:
                Michael.DeBinder Michael DeBinder (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2h Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h
                  4h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.