Workday Source

Polling Interval and Workday API rate limits

During each polling interval, the Workday Source will make a REST API request to fetch audit activity logs and another request to the RAAS API to fetch the Signon logs. The REST API can fetch a maximum of 100 records at a time and the RAAS API has a limit of 2GB. We recommend you do not set the polling interval below 10 min. 

States

The Workday Source reports errors, its health, and initialization status. Other than indicating that the source is healthy, you are also informed, in real-time, if the source is running into trouble communicating with Workday REST API, or if there's an error that requires user action indicated by Sumo Logic Health Events.

A Workday Source goes through the following states when created:

1. Pending: Once the Source is submitted, details are stored and the source is placed in a Pending state.

2. Started: A collection task is created on the hosted collector.

3. Initialized: Task configuration is complete in Sumo Logic.

4. Authenticated: The Source has successfully authenticated with Workday

5. Collecting: The Source is actively collecting data from Workday.

If the Source has any issues during any one of these states it is placed in an Error state.

Hover your mouse over the status icon to view a tooltip with details on the detected issue.

When you delete the source it is placed in a Stopping state and when it has successfully stopped it is deleted from your Hosted Collector.

On the Collection page, the Health and Status for Sources is displayed. Use Health Events to investigate issues with collection.

Error types

When Sumo Logic detects an issue it is tracked by Health Events. The following table shows the three possible error types, the reason the error would occur, if the Source attempts to retry, and the name of the event log in the Health Event Index.

JSON configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

The following table shows the config parameters for Workday Source.

Workday Source JSON example:

{
  "api.version":"v1",
  "source":{
    "config":{
      "name":"testWorkdaySource",
      "polling_interval_minutes":10,
      "refresh_token":"********",
      "workday_rest_api_endpoint":"https://wd2-impl-services1.workday.c...sumologic_dpt1",
      "refresh_token_endpoint":"https://wd2-impl-services1.workday.c...gic_dpt1/token",
      "client_id":"NTkzOWFkMjctY2QxNS00MDZiLTg2MWQtMjNiNzBiYzAxNTNk",
      "isu_username":"SumoLogic",
      "fields":{
        "_siemForward":false
      },
      "signon_report_url":"https://wd2-impl-services1.workday.c...Signons_-_Copy",
      "category":"workday_logs",
      "isu_password":"********",
      "client_secret":"********",
      "backfill_days":0
    },
    "schemaRef":{
      "type":"Workday"
    },
    "state":{
      "state":"Pending"
    },
    "sourceType":"Universal"
  }
}

Troubleshooting

After you configure your Source, you should check the status of the source in the Collectors page. In case the Source is not functioning as expected, you may see an error next to the Source Category column as shown below: 

The following section details how you can resolve various errors: 

1. Error:  401 Client Error: 401: invalid username or password

To resolve this

1. Check if you have such an authentication policy enabled. If by default your users' login via SSO then you may have to exclude the ISU Security Group to allow it to use username and password by creating a separate authentication policy.
2. Try changing the Session Timeout Minutes to 0 as shown in the article (https://www.sora.co/help/configuring-your-workday-integration).
3. Exempt user from password expiration (as shown in the article (https://www.sora.co/help/configuring-your-workday-integration)).