Correlation ID with Universal Login

[avanscoy]

By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Adding correlation_id functionality to Universal Login and Actions Event objects.

References

Testing

Local testing

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation for new/changed functionality in this PR or in auth0.com/docs
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not the default branch

[github-actions]

Summary

Status	Count
🔍 Total	52
✅ Successful	8
⏳ Timeouts	0
🔀 Redirected	1
👻 Excluded	43
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Redirects per input

Redirects in main/docs/customize/actions/explore-triggers/signup-and-login-triggers/login-trigger/post-login-event-object.mdx

• [200] https://www.okta.com/legal | Redirect: Followed 1 redirect resolving to the final status of: OK. Redirects: https://www.okta.com/legal --> https://www.okta.com/legal/
  Full Github Actions output

[mikemimik]

LGTM

Approval for:

• main/docs.json

[DabbingUnicorn]

How about we use "authentication flows" instead of "events"?

Correlation ID persists throughout the following authentication flows:

The reason is that there are several events associated with, for example, the "Signup" flow, so the use of "events" might not be accurate in this context.