auth0 / auth0-authorization-extension

Auth0 Extension that adds authorization features to your account
https://auth0.com/docs/extensions/authorization-extension/v2
Other
82 stars 54 forks source link

Bump authorization extension rule timeout #363

Open joshbetz opened 1 year ago

joshbetz commented 1 year ago

✏️ Changes

Doubles the timeout for the authorization extension rule to 10s. We've seen these requests can take 3-4s in a brand new environment. Any increase in latency can cause them to timeout.

πŸ“· Screenshots

If there were visual changes to the application with this change, please include before and after screenshots here. If it has animation, please use screen capture software like to make a gif.

πŸ”— References

Include at at least one link to an explanation + requirements for this change, and more if at all possible. Typically this is a Jira/GitHub Issue, but could also be links to Zendesk tickets, RFCs, rollout plan or Slack conversations (for Slack conversations, make sure you provide a summary of the conversation under β€œChanges”).

🎯 Testing

Describe how this can be tested by reviewers. Please be specific about anything not tested and reasons why.

  • Make sure you add unit and integration tests.
  • If this is on a hot path, add load or performance tests
  • Especially for dependency updates we also need to make sure that there is no impact on performance.

βœ…πŸš« This change has been tested in a Webtask

βœ…πŸš« This change has unit test coverage

βœ…πŸš« This change has integration test coverage

βœ…πŸš« This change has been tested for performance

πŸš€ Deployment

Can this change be merged at any time? What will the deployment of the change look like? Does this need to be released in lockstep with something else?

βœ…πŸš« This can be deployed any time

or ⚠️ This should not be merged until:

  • Other PR is merged because REASON
  • After date because REASON
  • Other condition: REASON

🎑 Rollout

Explain how the change will be verified once released. Manual testing? Functional testing?

In order to verify that the deployment was successful we will …

πŸ”₯ Rollback

Explain when and why we will rollback the change.

We will rollback if …

πŸ“„ Procedure

Explain how the rollback for this change will look like, how we can recover fast.

πŸ–₯ Appliance

Note to reviewers: ensure that this change is compatible with the Appliance.