Update to change TLS 1.3 cyphers to the IANA name and advise deprecat…

[avanscoy]

…ed ciphers

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

The purpose of this PR is to:

• Update existing ciphers from the former name to the IANA names
• Advise the ciphers up for deprecation in June of 2026 with a link to the deprecation notice already in Docs

References

https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml

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

[nick-gagliardi]

Suggested change

	Although they remain available in some environments, the following TLS 1.2 cipher suites are deprecated and **scheduled to become unsupported starting June 2026**. To learn more, read [Weak TLS 1.2 Cipher Suites](/docs/troubleshoot/product-lifecycle/deprecations-and-migrations#weak-tls-1-2-cipher-suites).
	**scheduled to become unsupported starting June 2026**.

This phrasing reads a bit clunky to me. Can we say something like, "Although they remain available in some environments, the following TLS 1.2 cipher suites are deprecated and will reach end-of-support in June 2026."

I think we should also reserve bold for UI elements per style guide. Let me know what you think!

[avanscoy]

Great call-out. I'll update with another commit so you can approve. Thanks for the review!