Okta : Fix the issue report in VTT-7228

[rakhimundhada15]

Problem Description

After upgrading the Node.js version to 22, the build process for the collector automatically picked up the latest minor version of okta-sdk-node-js (7.2.1), replacing the previously used version 7.1.1. This change started causing the following error:

The collector is reporting the following configuration errors: **Okta HTTP 400 E0000030 The date format in your query is not recognized. Please enter dates using the Internet Date/Time Format profile of ISO 8601.**

https://developer.okta.com/docs/reference/error-codes/?q=E0000030

Solution Description

1. The issue occurred because Okta changed the type of query parameters in version 7.2.0 of the okta-sdk-node-js package—from Date to string. However, this change was not reflected in the Okta documentation example.
   which still show usage with Date types. Upon reviewing the latest SDK, we confirmed that the expected type is now string. Therefore, we updated our implementation to use string instead of Date.

2. Additionally, to prevent similar issues in the future, we updated the package.json to use a tilde (~) version specifier for okta-sdk-node-js. This ensures that only patch updates are picked up automatically, avoiding unintended minor version upgrades that could break existing functionality.

[al-cibot]

CI Service Job Number 1116 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1116 -g

Stages Run:

• PR Test

[imranalisyed506]

+1

[rakhimundhada15]

build-collector-okta

[al-cibot]

CI Service Job Number 1117 Logs - SUCCESS

alps ci job-logs --organization alertlogic --repository paws-collector --job-num 1117 -g

Stages Run:

• build-collector-okta
• file_packager_0ca60e