|
1 | 1 | --- |
2 | 2 | pcx_content_type: changelog |
3 | 3 | title: Access |
4 | | -release_notes_file_name: |
5 | | - - access |
6 | 4 | head: |
7 | 5 | - tag: title |
8 | 6 | content: Access Changelog |
9 | 7 | description: Review recent changes to Cloudflare Access. |
10 | | - |
11 | 8 | --- |
12 | 9 |
|
13 | | -import { ProductReleaseNotes, Render } from "~/components" |
| 10 | +import { ProductChangelog } from "~/components"; |
| 11 | + |
| 12 | +{/* <!-- All changelog entries live in src/content/changelogs/access/. */} |
| 13 | + |
| 14 | +<ProductChangelog product="access" hideEntry="2024-06-16-cloudflare-one" /> |
| 15 | + |
| 16 | +## 2025-02-12 |
| 17 | + |
| 18 | +**Access policies support filtering** |
| 19 | + |
| 20 | +You can now filter Access policies by their action, selectors, rule groups, and assigned applications. |
| 21 | + |
| 22 | +## 2025-02-11 |
| 23 | + |
| 24 | +**Private self-hosted applications and reusable policies GA** |
| 25 | + |
| 26 | +[Private self-hosted applications](/cloudflare-one/applications/non-http/self-hosted-private-app/) and [reusable Access policies](/cloudflare-one/policies/access/policy-management/) are now generally available (GA) for all customers. |
| 27 | + |
| 28 | +## 2025-01-21 |
| 29 | + |
| 30 | +**Access Applications support private hostnames/IPs and reusable Access policies.** |
| 31 | + |
| 32 | +Cloudflare Access self-hosted applications can now be defined by [private IPs](/cloudflare-one/applications/non-http/self-hosted-private-app/), [private hostnames](/cloudflare-one/applications/non-http/self-hosted-private-app/) (on port 443) and [public hostnames](/cloudflare-one/applications/configure-apps/self-hosted-public-app/). Additionally, we made Access policies into their own object which can be reused across multiple applications. These updates involved significant updates to the overall Access dashboard experience. The updates will be slowly rolled out to different customer cohorts. If you are an Enterprise customer and would like early access, reach out to your account team. |
| 33 | + |
| 34 | +## 2025-01-15 |
| 35 | + |
| 36 | +**Logpush for SSH command logs** |
| 37 | + |
| 38 | +Enterprise customers can now use Logpush to export SSH command logs for Access for Infrastructure targets. |
| 39 | + |
| 40 | +## 2024-12-04 |
| 41 | + |
| 42 | +**SCIM GA for Okta and Microsoft Entra ID** |
| 43 | + |
| 44 | +Cloudflare's SCIM integrations with [Okta](/cloudflare-one/identity/idp-integration/okta/#synchronize-users-and-groups) and [Microsoft Entra ID](/cloudflare-one/identity/idp-integration/entra-id/#synchronize-users-and-groups) (formerly AzureAD) are now out of beta and generally available (GA) for all customers. These integrations can be used for Access and Gateway policies and Zero Trust user management. Note: This GA release does not include [Dashboard SSO SCIM](/fundamentals/setup/account/account-security/scim-setup/) support. |
| 45 | + |
| 46 | +## 2024-10-23 |
| 47 | + |
| 48 | +**SSH with Access for Infrastructure** |
| 49 | + |
| 50 | +Admins can now use [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) to manage privileged access to SSH servers. Access for Infrastructure provides improved control and visibility over who accessed what service and what they did during their SSH session. Access for Infrastructure also eliminates the risk and overhead associated with managing SSH keys by using short-lived SSH certificates to access SSH servers. |
| 51 | + |
| 52 | +## 2024-08-26 |
| 53 | + |
| 54 | +**Reduce automatic seat deprovisioning minimum to 1 month, down from 2 months.** |
| 55 | + |
| 56 | +Admins can now configure Zero Trust seats to [automatically expire](/cloudflare-one/identity/users/seat-management/#enable-seat-expiration) after 1 month of user inactivity. The previous minimum was 2 months. |
| 57 | + |
| 58 | +## 2024-06-06 |
| 59 | + |
| 60 | +**Scalability improvements to the App Launcher** |
| 61 | + |
| 62 | +Applications now load more quickly for customers with a large number of applications or complex policies. |
| 63 | + |
| 64 | +## 2024-04-28 |
| 65 | + |
| 66 | +**Add option to bypass CORS to origin server** |
| 67 | + |
| 68 | +Access admins can [defer all CORS enforcement to their origin server](/cloudflare-one/identity/authorization-cookie/cors/#bypass-options-requests-to-origin) for specific Access applications. |
| 69 | + |
| 70 | +## 2024-04-15 |
| 71 | + |
| 72 | +**Zero Trust User identity audit logs** |
| 73 | + |
| 74 | +All user identity changes via SCIM or Authentication events are logged against a user's registry identity. |
| 75 | + |
| 76 | +## 2024-02-22 |
| 77 | + |
| 78 | +**Access for SaaS OIDC Support** |
| 79 | + |
| 80 | +Access for SaaS applications can be setup with OIDC as an authentication method. OIDC and SAML 2.0 are now both fully supported. |
| 81 | + |
| 82 | +## 2024-02-22 |
| 83 | + |
| 84 | +**WARP as an identity source for Access** |
| 85 | + |
| 86 | +Allow users to log in to Access applications with their WARP session identity. Users need to reauthenticate based on default session durations. WARP authentication identity must be turned on in your device enrollment permissions and can be enabled on a per application basis. |
| 87 | + |
| 88 | +## 2023-12-20 |
| 89 | + |
| 90 | +**Unique Entity IDs in Access for SaaS** |
| 91 | + |
| 92 | +All new Access for SaaS applications have unique Entity IDs. This allows for multiple integrations with the same SaaS provider if required. The unique Entity ID has the application audience tag appended. Existing apps are unchanged. |
| 93 | + |
| 94 | +## 2023-12-15 |
| 95 | + |
| 96 | +**Default relay state support in Access for SaaS** |
| 97 | + |
| 98 | +Allows Access admins to set a default relay state on Access for SaaS apps. |
| 99 | + |
| 100 | +## 2023-09-15 |
| 101 | + |
| 102 | +**App launcher supports tags and filters** |
| 103 | + |
| 104 | +Access admins can now tag applications and allow users to filter by those tags in the App Launcher. |
| 105 | + |
| 106 | +## 2023-09-15 |
| 107 | + |
| 108 | +**App launcher customization** |
| 109 | + |
| 110 | +Allow Access admins to configure the App Launcher page within Zero Trust. |
| 111 | + |
| 112 | +## 2023-09-15 |
| 113 | + |
| 114 | +**View active Access user identities in the dashboard and API** |
| 115 | + |
| 116 | +Access admins can now view the full contents of a user's identity and device information for all active application sessions. |
| 117 | + |
| 118 | +## 2023-09-08 |
| 119 | + |
| 120 | +**Custom OIDC claims for named IdPs** |
| 121 | + |
| 122 | +Access admins can now add custom claims to the existing named IdP providers. Previously this was locked to the generic OIDC provider. |
| 123 | + |
| 124 | +## 2023-08-02 |
| 125 | + |
| 126 | +**Azure AD authentication contexts** |
| 127 | + |
| 128 | +Support Azure AD authentication contexts directly in Access policies. |
14 | 129 |
|
15 | | -<Render file="changelog-note" /> |
| 130 | +## 2023-06-23 |
16 | 131 |
|
17 | | -{/* <!-- All changelog entries live in src/content/changelogs/access.yaml. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */} |
| 132 | +**Custom block pages for Access applications** |
18 | 133 |
|
19 | | -<ProductReleaseNotes /> |
| 134 | +Allow Access admins to customize the block pages presented by Access to end users. |
0 commit comments