Merge branch 'production' into workers-ai-changelog-04-10

Author: kodster28

public/__redirects

@@ -716,7 +716,10 @@
 /learning-paths/cybersafe/concepts/what-is-area1/ /learning-paths/cybersafe/concepts/what-is-email-security/ 301
 /learning-paths/cybersafe/area1-onboarding/ /learning-paths/cybersafe/email-security-onboarding/ 301
 
-
+## zero-trust-web access / clientless-access
+/learning-paths/zero-trust-web-access/concepts/reverse-proxy-server/ https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/ 301
+/zero-trust-web-access/concepts/zero-trust/ https://www.cloudflare.com/learning/security/glossary/what-is-zero-trust/ 301
+/learning-paths/zero-trust-web-access/concepts/zero-trust-web-access/ /learning-paths/clientless-access/concepts/what-is-clientless-access/ 301
 
 ## dns-filtering / secure-internet-traffic
 /learning-paths/dns-filtering/ /learning-paths/secure-internet-traffic/ 301
@@ -743,7 +746,7 @@
 /learning-paths/secure-internet-traffic/ /learning-paths/secure-internet-traffic/concepts/ 301
 /learning-paths/secure-o365-email/ /learning-paths/secure-o365-email/concepts/ 301
 /learning-paths/workers/ /learning-paths/workers/concepts/ 301
-/learning-paths/zero-trust-web-access/ /learning-paths/zero-trust-web-access/concepts/ 301
+/learning-paths/clientless-access/ /learning-paths/clientless-access/concepts/ 301
 /learning-paths/application-security/default-traffic-security/security-level/ /learning-paths/application-security/default-traffic-security/browser-integrity/ 301
 
 # more redirects in the /dynamic/ section
@@ -1916,6 +1919,8 @@
 /learning-paths/dns-filtering/create-policy/* /learning-paths/secure-internet-traffic/build-dns-policies/:splat 301
 ## Secure your Internet Traffic
 /learning-paths/secure-internet-traffic/connect-devices/* /learning-paths/secure-internet-traffic/connect-devices-networks/:splat 301
+## Zero Trust Web Access --> Clientless Access
+/learning-paths/zero-trust-web-access/* /learning-paths/clientless-access/:splat 301
 
 # Cloudflare for SaaS
 /ssl/ssl-for-saas/common-tasks/* /cloudflare-for-platforms/cloudflare-for-saas/ 301

src/assets/images/changelog/access/example-scim-log.png

@@ -0,0 +1,11 @@
+---
+title: Cloudflare Zero Trust SCIM User and Group Provisioning Logs
+description: View all user and group updates, creation and deletion events made via SCIM across all of your IdP instances in one place
+date: 2025-04-09T6:00:00Z
+---
+
+[Cloudflare Zero Trust SCIM provisioning](/cloudflare-one/identity/users/scim) now has a full audit log of all create, update and delete event from any SCIM Enabled IdP. The [SCIM logs](/cloudflare-one/insights/logs/scim-logs/) support filtering by IdP, Event type, Result and many more fields. This will help with debugging user and group update issues and questions.
+
+SCIM logs can be found on the Zero Trust Dashboard under Logs -> SCIM provisioning
+
+![Example SCIM Logs](~/assets/images/changelog/access/example-scim-log.png)

src/content/changelog/access/2025-04-09-SCIM-provisioning-logs.mdx

@@ -0,0 +1,7 @@
+---
+pcx_content_type: navigation
+title: Deploy clientless access
+external_link: /learning-paths/clientless-access/concepts/
+sidebar:
+  order: 3
+---

src/content/docs/cloudflare-one/implementation-guides/clientless-access.mdx

@@ -31,8 +31,8 @@ Implementation guides cover deployment steps and best practices for specific Clo
 </LinkTitleCard>
 
 <LinkTitleCard
-	title="Deploy Zero Trust Web Access"
-	href="/learning-paths/zero-trust-web-access/concepts/"
+	title="Deploy clientless access"
+	href="/learning-paths/clientless-access/concepts/"
 	icon="laptop"
 >
 	Secure access to internal web applications without a device client.

src/content/docs/cloudflare-one/implementation-guides/index.mdx

@@ -49,7 +49,7 @@ Create a new Workers project by running the following command:
     	product="workers"
     	params={{
     	category: "hello-world",
-    	type: "Worker + Assets",
+    	type: "SSR / full-stack app",
     	lang: "TypeScript",
     	}}
     />

src/content/docs/cloudflare-one/implementation-guides/zero-trust-web-access.mdx

@@ -20,6 +20,6 @@ Access applications have an inherently flexible and powerful domain structure ca
 
 ### Multiple domains in an application
 
-Many customers who have workflows designed around internal web applications, especially those that were built internally, often see challenges related to interdependencies on multiple internal services. Separately, there can be challenges related to SPAs (Single-Page Applications) that make onboarding to a Zero Trust Web Access service difficult. For example, an application may have iFrames or other embedded systems that rely on different internal and/or external addresses.
+Many customers who have workflows designed around internal web applications, especially those that were built internally, often see challenges related to interdependencies on multiple internal services. Separately, there can be challenges related to SPAs (Single-Page Applications) that make deploying clientless access difficult. For example, an application may have iFrames or other embedded systems that rely on different internal and/or external addresses.
 
-If your internal service operates in this way, we recommend specifying multiple top-level domains in a single Access application. Otherwise, if the goal of using multiple domains is to streamline or simplify policy creation, we recommend making one primary domain per application, and automating the rest of your deployment [using Terraform](/learning-paths/zero-trust-web-access/terraform/) or another Infrastructure as Code (IaC) service.
+If your internal service operates in this way, we recommend specifying multiple top-level domains in a single Access application. Otherwise, if the goal of using multiple domains is to streamline or simplify policy creation, we recommend making one primary domain per application, and automating the rest of your deployment [using Terraform](/learning-paths/clientless-access/terraform/) or another Infrastructure as Code (IaC) service.

src/content/docs/d1/tutorials/using-read-replication-for-e-com/index.mdx

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Now that you have [connected your private applications](/learning-paths/zero-trust-web-access/connect-private-applications/) to Cloudflare, secure those applications behind Cloudflare Access.
+Now that you have [connected your private applications](/learning-paths/clientless-access/connect-private-applications/) to Cloudflare, secure those applications behind Cloudflare Access.
 
 ## Objectives