Question
Evoke Technologies
IN
Last activity: 3 May 2024 10:18 EDT
Queries on Pega Constellation UI.
Hi All, Can you please help us with the below queries :
1. For a constellation application built on top of traditional application : does the old Jsession cookie approach remains for the user session identification ?
2.For a new Constellation application, is the same completely stateless ? Like no user session management is required ? How is system able to identify the user session if the session is terminated after each DX API call ?
3. Does the new Constellation application prefers a specific authentication method over others ?
4. Can the Constellation UI part be deployed as a separate application, assuming all the data retrievals/updates are done via DX API ? Like can we use Pega Constellation as a front end application ?
Pegasystems Inc.
CA
1. I believe so.
2.The shift to a stateless architecture comes with lots of upside, but it also results in some significant change. The Constellation application is communicating with a stateless server and so the requestor session is terminated after each request. As a result, the process of debugging an application has changed significantly. The clipboard is released after each Constellation DX API call. That means it is no longer possible to run Clipboard from the end-user portal or run it from Dev Studio and switch to the user portal thread to investigate live data. Instead of the Clipboard, there are numerous powerful debugging tools available for use with Constellation applications.
3.By default, Constellation SDKs use the OAuth 2.0 authentication type with the Public authorization code grant flow. This authentication type supports both modes of application implementations, embedded application and portal application
4 Constellation UI uses DX API to render the data on the screen.
Evoke Technologies
IN
@RameshSangili - Thanks Ramesh for your response.
For point number 2. I agree that when constellation interacts with the pega engine, it is in stateless form and the requestor session is terminated post every DX API call. But what about the main session id that was created when the user logged in ? How exactly the same is managed in Constellation ?
For point number 4: Is there a possibility to create a front end application using the Constellation UI/UX. Just the constellation design system and not the Pega Engine. The idea is to create the front end using Constellation UI/UX and then interact with Pega applications via DX API.
Pegasystems Inc.
CA
Constellation architecture is built on top of the Pega Engine. Please find the link for more details.
https://academy.pega.com/topic/introduction-constellation-architecture/v1/in/70261/70291