Processed new reference files
This commit is contained in:
@@ -34,15 +34,15 @@ Fixed an issue where, when the GlobalProtect app was installed on Windows device
|
||||
|
||||
## GPC-18426
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was configured with the Disable GlobalProtect set to Allow with Ticket, the app did not display the correct Disable Duration time.
|
||||
Fixed an issue where when the GlobalProtect app was configured with the **Disable GlobalProtect** set to **Allow with Ticket**, the app did not display the correct Disable Duration time.
|
||||
|
||||
## GPC-18336
|
||||
|
||||
Fixed an issue where the GlobalProtect app got automatically connected after a system reboot even though the connection method configured was On-Demand.
|
||||
Fixed an issue where the GlobalProtect app got automatically connected after a system reboot even though the connection method configured was **On-Demand**.
|
||||
|
||||
## GPC-18318
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was connected to the internal gateway, the app displayed the message as Connected - Inter.... instead of Connected - Internal.
|
||||
Fixed an issue where, when the GlobalProtect app was connected to the internal gateway, the app displayed the message as **Connected - Inter....** instead of **Connected - Internal**.
|
||||
|
||||
## GPC-18281
|
||||
|
||||
@@ -54,7 +54,7 @@ Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe
|
||||
|
||||
## GPC-18230
|
||||
|
||||
Fixed an issue where, when the user entered credentials during SAML authentication after the set internal login timer, the app displayed an authentication failed message without providing the reason. The Retry button on the app web interface did not work properly when using an embedded browser for authentication. The Retry button was not fully visible on the embedded browser.
|
||||
Fixed an issue where, when the user entered credentials during SAML authentication after the set internal login timer, the app displayed an authentication failed message without providing the reason. The **Retry** button on the app web interface did not work properly when using an embedded browser for authentication. The **Retry** button was not fully visible on the embedded browser.
|
||||
|
||||
## GPC-18175
|
||||
|
||||
@@ -98,7 +98,7 @@ Fixed an issue where the GlobalProtect HIP check did not detect McAfee Total Pro
|
||||
|
||||
## GPC-18036
|
||||
|
||||
Fixed an issue where, when the No direct access to local network option was enabled on the GlobalProtect app with access routes excluded from the GlobalProtect VPN tunnel, the feature did not work as expected when Endpoint Traffic Policy Enforcement was enabled.
|
||||
Fixed an issue where, when the **No direct access to local network** option was enabled on the GlobalProtect app with access routes excluded from the GlobalProtect VPN tunnel, the feature did not work as expected when Endpoint Traffic Policy Enforcement was enabled.
|
||||
|
||||
## GPC-17936
|
||||
|
||||
@@ -106,15 +106,15 @@ Fixed an issue where the Conditional Connect method did not work as expected and
|
||||
|
||||
## GPC-17921
|
||||
|
||||
Fixed an issue where, when the language was set to Japanese, the time to connect was not displayed properly when Disconnect Timeout for the app was configured.
|
||||
Fixed an issue where, when the language was set to Japanese, the time to connect was not displayed properly when **Disconnect Timeout** for the app was configured.
|
||||
|
||||
## GPC-17896
|
||||
|
||||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: Cannot Verify Server Certificate of Gateway.
|
||||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: **Cannot Verify Server Certificate of Gateway**.
|
||||
|
||||
## GPC-17816
|
||||
|
||||
Fixed an issue ehere after entering CIE SAML authentication credentials to refresh an expired explicit proxy token or cookie when connected in Tunnel and Proxy mode or proxy mode, the GlobalProtect app got stuck while retrieving the portal configuration.
|
||||
Fixed an issue ehere after entering CIE SAML authentication credentials to refresh an expired explicit proxy token or cookie when connected in [Tunnel and Proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-tunnel-and-proxy-mode) or [proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-proxy-mode), the GlobalProtect app got stuck while retrieving the portal configuration.
|
||||
|
||||
## GPC-17795
|
||||
|
||||
@@ -126,7 +126,7 @@ Fixed an issue where, when the GlobalProtect app was installed on devices runnin
|
||||
|
||||
## GPC-17762
|
||||
|
||||
Fixed an issue when the GlobalProtect app was configured with the option Allow User to Disable GlobalProtect App with comment, the option did not work as expected.
|
||||
Fixed an issue when the GlobalProtect app was configured with the option **Allow User to Disable GlobalProtect App** with comment, the option did not work as expected.
|
||||
|
||||
## GPC-17748
|
||||
|
||||
@@ -138,15 +138,15 @@ Fixed an issue where, when the GlobalProtect app was connected through the Prism
|
||||
|
||||
## GPC-17728
|
||||
|
||||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: Cannot Verify Server Certificate of Gateway.
|
||||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: **Cannot Verify Server Certificate of Gateway**.
|
||||
|
||||
## GPC-17460
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows 10 or 11 devices, and when the user tried to authenticate using SAML authentication, the app did not display the Term of Use pop-up on the Welcome page properly.
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows 10 or 11 devices, and when the user tried to authenticate using SAML authentication, the app did not display the **Term of Use** pop-up on the **Welcome** page properly.
|
||||
|
||||
## GPC-17398
|
||||
|
||||
Fixed an issue where the GlobalProtect app SettingsConnection tab did not display the Assigned IP Address(es) and Gateway IP Address properly.
|
||||
Fixed an issue where the GlobalProtect app **Settings** > **Connection** tab did not display the **Assigned IP Address(es)** and **Gateway IP Address** properly.
|
||||
|
||||
## GPC-17206
|
||||
|
||||
@@ -154,7 +154,7 @@ Fixed an issue where, when Internal Host Detection (IHD) was enabled but failed
|
||||
|
||||
## GPC-17161
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect app failed to reconnect and continued to stay in the Connecting state after the device woke up from Modern Standby mode.
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect app failed to reconnect and continued to stay in the **Connecting** state after the device woke up from Modern Standby mode.
|
||||
|
||||
## GPC-17099
|
||||
|
||||
@@ -162,7 +162,7 @@ When the GlobalProtect app for Windows is upgraded to version 6.0.5, devices wit
|
||||
|
||||
## GPC-17001
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running on macOS, the app did not display the Connect button and Refresh Connection button properly.
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running on macOS, the app did not display the **Connect** button and **Refresh Connection** button properly.
|
||||
|
||||
## GPC-16978
|
||||
|
||||
@@ -170,7 +170,7 @@ Fixed an issue where the GlobalProtect app took a long time to establish a conne
|
||||
|
||||
## GPC-16851
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the app did not try to auto-connect to the gateway after exceeding the Disable Timeout Value.
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the app did not try to auto-connect to the gateway after exceeding the **Disable Timeout Value**.
|
||||
|
||||
## GPC-16397
|
||||
|
||||
@@ -186,7 +186,7 @@ Fixed an issue where, when the GlobalProtect app was installed on devices runnin
|
||||
|
||||
## GPC-15968
|
||||
|
||||
Fixed an issue where the GlobalProtect app was stuck in Connecting state when users failed to authenticate with SAML and using an embedded browser. Users were unable to disconnect the app and had to reboot the device.
|
||||
Fixed an issue where the GlobalProtect app was stuck in **Connecting** state when users failed to authenticate with SAML and using an embedded browser. Users were unable to disconnect the app and had to reboot the device.
|
||||
|
||||
## GPC-15262
|
||||
|
||||
|
||||
Reference in New Issue
Block a user