Constellation Portal 401 error after upgrading to 25.1.1 version
After upgrading the Constellation Platform to 25.1.1, portals in all applications stopped working. Here's the error from network tab:
https://<host_name>.pegalabs.io/prweb/app/<application_name>/api/application/v2/portals/WebPortal
Request Method
GET
Status Code
401 Unauthorized
Remote Address
Proprietary information hidden:443
Referrer Policy
strict-origin-when-cross-origin
DSS:
ConstellationSvcURL: https://community.constellation.pega.io/c11n-appstatic (tried also https://prod.constellation.pega.io/c11n-appstatic and
https://staging.constellation.pega.io/c11n-appstatic)
ConstellationPegaStaticURL: https://prod-cdn.constellation.pega.io/fea-cs-prod (tried also: https://cs-cdn.constellation.pega.io/prod)
We're using Basic authentication
Since it is Pega Labs instance, the support ticket was initially created for Pega Labs team, but have since been advised it doesn't have much to do with infrastructure scope
Accepted Solution
Updated: 11 Dec 2025 2:54 EST
Pegasystems Inc.
US
@PatrykM8 There might an issue with a MyCar auth, I noticed the following in the logfile:
1 related to applies-to class 'Code-Security', but were defined in rulesets which are not in your rulesetlist: 'MyCar:01-01-01'. com.pega.pegarules.pub.generator.RuleNotFoundException: Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'MYCAR_CUSTOMAUTH' that applies to 'Code-Security'. There were 1 rules with this name in the rulebase, but none matched this request.
2025-12-10 10:33:45,685 [sse-nio-9443-exec-27] [ STANDARD] [ ] [ PegaRULES:8] (hentication.AuthenticationUtil) ERROR hidden|x.x.x.x|Rest|application|v2|portals_var7cdd8ca233096dcf898922fd339708ed|ACV00CIO1SV9DHH6QBOM57BKRJ7W9G8PXA ACV00CIO1SV9DHH6QBOM57BKRJ7W9G8PXA - Problem executing activity: Code-Security.MyCar_CustomAuth
AI4Process Ltd.
GB
@PhilipShannon Thanks. The issue was with the application service package that was referencing auth service that the user didn't have access with the ruleset stack. Reverting to the default OAuth 2.0 fixed the problem