Issue
Developers can add a combination of a logo and an icon to the main navigation menu to give Portals a distinct visual identity.
In certain instances, the expected logo is not displayed when the user logs into the portal. Instead, the alt text "Application logo" is shown with the standard broken image icon.
Steps to Reproduce
- Build an application on Pega Constellation™.
- Configure the application portal with a custom application logo in App Studio>>n>>>Select/Save file.
- Log into the portal. The custom logo is not loaded in the portal at run time.
Symptoms
In the browser network trace the request for the application logo returns a 400 Bad Request result.
Root Cause
The image must be synced to the Constellation Application Static (AppStatic) Service for the image to be returned to the user's browser request. Issues arise when this step has not occurred.
Causes of sync issues:
-
A known issue where AppStatic sync is not working as designed due to insufficient detail in the JWT token that describes the permissions for the user, which prevents proper access to the Constellation AppStatic Service data.
-
Invalid configuration where AppStatic Service has not been deployed, configured or referenced through the constellationSvcUrl DSS.
Suggested Troubleshooting
Steps to troubleshoot application image sync issues:
-
Keep current with Pega software updates
-
Ensure that the AppStatic Service version is the same or higher than 1.31.0. This step is only relevant for on-premises and Client-managed cloud deployments and if troubleshooting scenarios applications on Pega platform releases earlier than Pega '24.
-
Deploy the latest Pega Platform™ patch. The below patches resolved authentication errors during image syncing steps:
-
25.1.0 or later
-
24.2.1
-
24.1.3
-
23.1.5
-
-
- If these patches cannot be installed, contact the Pega Support team to request the relevant hotfix for your release:
- 24.2.0 (HFIX-C339)
- 24.1.2 (HFIX-C337)
- 24.1.1 (HFIX-C338)
- 24.1.0 (HFIX-C340)
- 23.1.4 (HFIX-C333)
- 23.1.3 (HFIX-C334)
- 23.1.2 (HFIX-C335)
- 23.1.1 (HFIX-C315)
- 23.1.0 (HFIX-C336)
- 8.8.5 (HFIX-C383)
- 8.7.6 (HFIX-C384)
A restart is required after the hotfix is installed. After the restart, you' will need to open the UTILITY library and click the button.
-
Verify that the Sync to the Constellation AppStatic Service exists (Pre-25.1 Pega Platform Versions only)
To set up the AppStatic Service and refer to it in the ConstellationSvcURL Dynamic System Setting (DSS), follow these steps:
-
Install and configure the AppStatic Service to host custom assets.
-
Configure the ConstellationSvcURL DSS to point to the AppStatic Service.
-
Wait for the synchronization of custom static assets to complete.
-
Verify that the custom logo is displayed in the portal header.
More details can be found in Configuring your Pega Platform to use the Constellation AppStatic Service. and Configuring Constellation Application Static Service.
-
Confirm the Logo Image Exists and Matches Request
-
Check that the image being requested by the browser exists as a binary file in your instance of Pega Platform. The browser network request should show a request for an image in a format similar to the below.
WEBWB!APPLICATIONLOGO20251017T152411.991 GMT!PNG
-
In Pega Platform '24 and earlier, this binary file will also need to be synced to the Constellation AppStatic Service since this is where the browser will request it from.
-
Re-upload Image if needed
If the binary file is missing:
-
Re-upload the image via the portal configuration.
-
Resave Rule-File-Binary to sync individual assets.
-
Resave the Application rule to trigger a full resync of assets (Localization rules, DX Components, and Images)
-
Log out and log back in and retest the portal.
-
Review the Sync Logs (Pre-'25.1 Pega Platform Versions only)
-
Enable the pxStaticContentSync logger category in Admin Studio to see debug entries for the sync .
-
For on-premises installations, check AppStatic log files for sync errors.
-
Identify Sync Failures
-
Look for 400 or 401 errors in logs.
-
Check for authentication or permission issues.
Example of expected static Log entries for sync:
INFO: 1760713485077 service.cacheAssets() auth callback(/usr/src/app//customers, false, da8ff0ef94c7, Playground, undefined, BINARY)
INFO: 1760713485077 assets.cacheAssets() : BINARY WEBWB!APPLICATIONLOGO20251017T150443.206 GMT!PNG, Playground, 2025-10-17T15:04:43.304Z
POST 201 /c11n-appstatic/8.24.52-349/v102/assetsUpdate 58ms
Example static Log entries for failed request:
ERROR: Fri, 17 Oct 2025 15:04:58 GMT "WEBWB!APPLICATIONLOGO20251013T161956.677 GMT!PNG has not been synced for this environment"
GET 400 /c11n-appstatic/v102/app/playground/image/WEBWB!APPLICATIONLOGO20251013T161956.677 GMT!PNG 8ms
Example static Log entries for failed sync:
ERROR: Mon, 13 Oct 2025 05:59:42 GMT error authenticate in httpmain.assetsUpdate() permission undefined undefined
POST 401 /c11n-appstatic/8.24.1-195/v102/assetsUpdate 2ms
If you see a 400 request for an application image for which there is no binary file, then it is likely not synced to the AppStatic Service. You will need to resync the image with the service as outlined in this document.
7. Ensure that any custom certificates have been added to Java Keystore
The need to add certificates may depend on whether the customer is using on-premises or cloud solutions, and how certificates are created.
Publicly trusted authorities (like DigiCert) are included by default, but certificates from Amazon, Google, or Microsoft may need to be added manually.
If a client creates their own certificates, these must be manually added to the keystore.
If you need guidance on updating the certificates please contact Global Client Support for further help with this.
References
Deploying the Constellation Application Static Service
Configuring Constellation Application Static Service
Withdrawn and deprecated features
Unable to set a custom logo for a portal in Contellation App Studio