From 16ebf3e756f33c6d292506dc87605294d5830ebe Mon Sep 17 00:00:00 2001 From: Ricardo Martin Date: Mon, 8 Dec 2025 10:43:13 +0100 Subject: [PATCH] Move link changed for developer.mozilla.org (#44668) Closes #44661 Signed-off-by: rmartinc --- docs/documentation/upgrading/topics/changes/changes-26_0_0.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/upgrading/topics/changes/changes-26_0_0.adoc b/docs/documentation/upgrading/topics/changes/changes-26_0_0.adoc index 4ca8ec21456..3a2ae5c06a1 100644 --- a/docs/documentation/upgrading/topics/changes/changes-26_0_0.adoc +++ b/docs/documentation/upgrading/topics/changes/changes-26_0_0.adoc @@ -443,7 +443,7 @@ Make sure to update your code to `await` these methods. == A secure context is now required -Keycloak JS now requires a link:https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts[secure context] to run. The reason for this is that the library now uses the Web Crypto API for various cryptographic functions. This API is only available in secure contexts, which are contexts that are served over HTTPS, `localhost` or a `.localhost` domain. If you are using the library in a non-secure context you'll need to update your development environment to use a secure context. +Keycloak JS now requires a link:https://developer.mozilla.org/en-US/docs/Web/Security/Defenses/Secure_Contexts[secure context] to run. The reason for this is that the library now uses the Web Crypto API for various cryptographic functions. This API is only available in secure contexts, which are contexts that are served over HTTPS, `localhost` or a `.localhost` domain. If you are using the library in a non-secure context you'll need to update your development environment to use a secure context. = Stricter startup behavior for build-time options