Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

chore[oidc-middleware]: Updating UUID version #1010

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

NovaAtWarren
Copy link
Contributor

Avoids this error message: Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
Potential security upgrade.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Adding Tests
  • Build related changes
  • CI related changes
  • Documentation changes
  • Other: Dependency Update

What is the current behavior?

N/A
Issue Number: N/A

What is the new behavior?

N/A

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Reviewers

Avoids deprecation message and insecure random usages
@oleksandrpravosudko-okta
Copy link
Contributor

Thanks for the contribution @NovaAtWarren.
Would you mind pushing yarn.lock update as well? (it looks like Travis build is failing because of missing lock file update)

@NovaAtWarren
Copy link
Contributor Author

Thanks for the contribution @NovaAtWarren.
Would you mind pushing yarn.lock update as well? (it looks like Travis build is failing because of missing lock file update)

Seems to me like a linting error in src/logout.js. Would you like me to change code to attempt a fix, or disable that linting rule for that line?

@NovaAtWarren
Copy link
Contributor Author

Finally, a package with proper SemVer. Bad side is this seems to have broken more than I initially thought. I'll have a closer look when I'm in front of a machine with a proper debugger.

Caused by update without reading migration guide.
Test > e2e > harness > server.js > DemoServer > start now uses random UUID like it used to.
Fixed error in linting where eslint complained about using Promise.reject. This should function the same, without the error while linting
@NovaAtWarren
Copy link
Contributor Author

Build now failing with Failed: Replace {clientSecret} with the client secret of your Application. You can copy it from the Okta Developer Console in the details for the Application you created. Follow these instructions to find it: https://bit.ly/finding-okta-app-credentials, and I don't have the testing client secret so I can't really do anything

@shuowu
Copy link
Contributor

shuowu commented Jun 15, 2021

@NovaAtWarren Thanks for your contribution. Since the PR need to pass Okta's internal CI system to get merged. We'll take over your PR at this point, and fix issues accordingly if needed.

Internal Ref: OKTA-404546

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants