After enabling MFA and FAS users may be unable to sign to Storefront published app with Anonymous account in other domain

After enabling MFA and FAS users may be unable to sign to Storefront published app with Anonymous account in other domain, with error "Incorrect Pin" Scenario: You may have Storefront, FAS Federated Authentication Service and VDAs in Domain A and there is another Domain Bhaving StoreFront and its...

How to land on the Favourites view under Apps on StoreFront 1912?

To set the default landing page to 'Favourites' under the apps tab in 1912. By default, the landing page is 'Home'. The below script would help in achieving the same: Step 1: In the Storefront console, navigate to 'Manage Receiver for Web Sites' Step 2: Click configure and browse to 'Client...

Unable to access StoreFront URL, error “can’t reach this page”

• In this scenario, the customer just built a test site running Virtual Apps 1912CU1 • He built one DDC, 2 StoreFront servers, and aleady created a Site and a StoreFront Store • When attempting to access the StoreFront URL, he gets an error saying “can’t reach this page” • Using the StoreFront...

VulnCheck KEV: CVE-2019-13608

Citrix StoreFront Server contains an XML External Entity XXE processing vulnerability that may allow an unauthenticated attacker to retrieve potentially sensitive information...

Change Password Option Not Available

Client Users Are Unable To See The Option "Change Password" Through Citrix Storefront Web...

Common Resolutions to “Cannot Complete Your Request” Error when connecting through Citrix Gateway

Symptoms or Error The “Cannot Complete Your Request” error is displayed whenconnecting through Citrix Gateway. However, this is an error could occur when connecting to StoreFront Server directly or through Load Balancer based on different deployment scenarios. To narrow down through which...

Cannot Complete Your Request Error only occurs to certain users connecting from ADC with Azure MFA over to Storefront

Certain users are receiving Cannot Complete Your Request Error when accessing site via ADC url and after entering their Azure MFA credentials and user is redirected to Storefront's URL, then the error is observed. On the Storefront Server we see the following Event: Log Name: Citrix Delivery...

After StoreFront upgrade server groups can no longer propagate changes.

Post upgrade of StoreFront component, propagation fails with below event on Initiating server: Event id 31. An error has occurred during the all server configuration update process. Citrix.DeliveryServices.ConfigurationReplication.Exceptions.ServerUpdateConfigurationException,...

"You cannot logon to the specified server" error when login to Storefront server.

Only certain users cannot log on to storefront. Following events can be seen on the storefront server : Security events logs : Event 4625, Microsoft Window security auditing Failure Information : Failure Reason : User not allowed to logon at this computer. Status : 0xC000006E Citrix Delivery...

WordPress Malware Setting Up SEO Shops

While recently looking over my honeypots, I discovered an infection where a malicious actor added a storefront on top of my existing WordPress installation. For background, this particular honeypot is a full instance of WordPress running on a Docker image...

Storefront 3.12 : SSON not working with Storefront and Microsoft Edge based on Chromium

Works with IE and all other browsers exceptMicrosoft Edge based on Chromium...

Citrix StoreFront Web GUI Assistant

StoreFront Web GUI DevlopedDate: 09/12/2013 Modified Date: 04/16/2020 Where to download ? Certain legacy Citrix tools are now available on request only. Please submit the request here - https://forms.gle/obA39PEz5qpDiSPq8 Once we verify your request, we will provide access to the download locatio...

Error: "Your logon has expired. Please log on again to continue." When Users Logon to StoreFront 1.2

After IT Administrators enable the ‘requireTokenConsistency’ parameter to ‘true ’ on StoreFront’s ‘store’ configuration file C:\inetpub\wwwroot\Citrix\Web.config users might not be able to access the resources. This feature is used to allow SmartAccess conditions to be passed from StoreFront...

Spree Authorization Issues Vulnerability

Spree is a personal developer of an open source mall developed using Ruby on Rails. An authorization issue vulnerability exists in Spree version 3.7.11, version 4.0.4, and versions prior to 4.1.11, which stems from an expired user token that can be used to access the storefront API v2 endpoint. A...

Token Validation Bypass

spreeapi is vulnerable to token validation bypass. Failure to check for the expiry of the doorkeepertoken allows an attacker to access Storefront API v2 endpoints using expired user tokens...

Storefront 1912 - Unable to upgrade the sole SF server

While upgrading the StoreFront server from 1903 to 1912.CU1, we get below error " An error occurred during installation . Please ensure all the required prerequisites have been installed - Citrix storefront"...

CVE-2020-15269

In Spree before versions 3.7.11, 4.0.4, or 4.1.11, expired user tokens could be used to access Storefront API v2 endpoints. The issue is patched in versions 3.7.11, 4.0.4 and 4.1.11. A workaround without upgrading is described in the linked advisory...

Code injection

In Spree before versions 3.7.11, 4.0.4, or 4.1.11, expired user tokens could be used to access Storefront API v2 endpoints. The issue is patched in versions 3.7.11, 4.0.4 and 4.1.11. A workaround without upgrading is described in the linked advisory...

CVE-2020-15269

The CVE applies to Spree releases prior to 3.7.11, 4.0.4, and 4.1.11, where expired user tokens could be reused to access Storefront API v2 endpoints. Root cause: expired tokens could authenticate to API v2; patch versions are 3.7.11, 4.0.4, and 4.1.11 (or newer). A workaround without upgrading i...

CVE-2020-15269 Expired token reuse in Spree

In Spree before versions 3.7.11, 4.0.4, or 4.1.11, expired user tokens could be used to access Storefront API v2 endpoints. The issue is patched in versions 3.7.11, 4.0.4 and 4.1.11. A workaround without upgrading is described in the linked advisory...