I created a C11N case type in Traditional (UIKit) application. While launching the constellation case, I’m observing 401 unauthorized response for the DXAPI requests. I also observed that the /token endpoint is not being invoked. Is there any additional steps required, such as creating the ‘oAuth client registration’..etc?
Also, no POST /cases API call, it directly invoking the GET /assignments/{assignID} API.
Yes, for a C11N Constellation app, an OAuth 2.0 Client Registration is required, but creating a random one is not sufficient. The client registration must be the one associated with the C11N application, and its credentials must be referenced by the app’s authentication/profile setup so the runtime can obtain an access token before DX API calls are made.
After creation, verify the client registration is correctly linked to the app/access group, regenerate the secret if the app was imported, and confirm the authentication profile/endpoints are pointing to that registration. If this wiring is wrong, the /token call may never happen and DX API requests will fail with 401.
Hi Ravi, As I mentioned in the description it is a UIKit application, in which I created a Constellation case type. Are the steps mentioned in the post that you pointed, still applicable for my scenario?
Yes, the authentication/OAuth guidance is still applicable even if the base application is UIKit, because a Constellation case type still runs through DX API and therefore needs the Constellation authentication setup.
In your scenario there are also additional coexistence steps to verify: generate the Traditional UI in Constellation assets/routing, make sure the operator has the PegaAPI role manually added and confirm the UI Kit - Constellation authentication/client registration setup is valid. For mixed UIKit + Constellation setups, authentication on both sides and in some cases potentially regenerating the client secret.
Hi Raghuveer,
As @RaviChandra mentioned, regenerate the secret and try again. If this issue still persists, Could you please confirm if you’re able to trigger the DX APIs through Postman/other tools to ensure the Authentication works fine?
The activity is exiting on the first step, as the entry condition is false (.pxUseDXAPI is false). As I mentioned earlier, I’m creating a constellation case type in traditional application. Could you assist me with this?
In a mixed UIKit + Constellation setup, simply creating a Constellation case type inside a traditional app does not automatically switch execution to DX API mode. That flag is typically set only when the request comes through the Constellation channel (DX API / React shell). In your usecase, if that .pxUseDXAPI is false, then request is still being treated as a traditional (non‑DX) interaction, so the Constellation flow is never actually engaged.
As a quick diagnosis-
Try creating the same case via Postman using DX API:
Could you please confirm how are you launching the case?
If it’s via a button/flow/action in UIKit → it will stay traditional. Constellation cases must be created via DX API or Constellation UI shell.
Can you try one of the 2 options and let us know the findings?
Option 1: Launch the case via DX API (e.g., /cases POST) or Constellation UI. Test via Postman first. If .pxUseDXAPI becomes true there, your issue is entry channel, not config. and ensure correct OAuth client + access token
Option 2: If you must trigger from UIKit, i.e. via a button/flow/action, you need to explicitly invoke DX APIs instead of using traditional case creation. For example, call a REST connector to your own DX API endpoint. Do not rely on traditional activities expecting .pxUseDXAPI = true, they won’t work reliably.
In the previous reply, you suggest to execute the pzRegisterConstellationAppAsOAuth2Client activity, in the context of Application record, to create the oAuth client registration instance. I’m trying to say that this activity is existing on the first step itself. Do I need to execute the steps that you suggest in the previous reply, or not? FYI, .pxUseDXAPI is in the context of Application rule record.
I understand the confusion. In that thread, it is mentioned that you can run pzRegisterConstellationAppAsOAuth2Client to manually register a UIKit application for Constellation in certain coexistence scenarios. However, you have mentioned that this activity is exiting immediately because its entry condition is false. I think because your the application is not a Constellation application but it is a UI Kit Application, .pxUseDXAPI is false at the Application rule level and the activity cannot create the OAuth client registration, because its entry condition depends on DX API being active.
It is not a best practice to try to force .pxUseDXAPI = true in a traditional UIKit app. The only appropriate way to make the pxUseDXAPI to true is either launch the case via DX API (e.g., POST /cases with a valid OAuth token) or launch it through the Constellation UI shell (React-based portal/channel).
If you need DX API behaviour from UIKit, you must explicitly call DX API via REST/connector, not via traditional activities. Since in your usecase you are creating Constellation case type inside a UI Kit app, we need to launch the case via DX API.
Hence I have suggested you try invoking the DX API directly via postman and check if it works and share the findings for better understanding.
Invoking the /cases DX API requires the access token. To get access token, I need client_id & client_secret. To get client_id/client_secret, I need oAuth client registration. How can I generate the oAuth client registration?
By default, Pega creates a new Oauth2.0 rule for every new applciation in Constellation. If you’re planning to reuse the Oauth2.0 generated by Pega, then you have to regenerate the secret and click on Save.
Please follow this documentation to Create a new one.
How does Pega recommending using the UIKit applications to have Constellation case types? What are the preparatory steps (as standard) for the co-existance? My requirement is - I’m on Infinity 24.2, I want to build a new Constellation case type in UIKit application.
