Question
Cox
US
Last activity: 8 Jul 2024 12:39 EDT
Need different experience based on the query params while logging using SSO
We have need to show different behaviours based on the query parameters while logging into pega using SSO.
Example: existing users log in using SSO link to log in to portal. BUt if the same user logs in using sso link with query parameters then we need to use those query parameters to how different behavior.
Please advise the design options. Tried few and while we are able to acheive diferent behaviour using query parameters.
for exisitng users, b/c the operator id already exists and does not create the operator and based on the showdesktop on the starting activity on the operator profile, it is logging into the portal without taking the query parameters.
Please help with different design approaches.
Updated: 28 Jun 2024 8:07 EDT
Pegasystems Inc.
GB
Based on the context, there are a few design options you could consider:
- Customize the SSO Authentication Service to call an activity that extracts the query parameters. This is mentioned in reference 2. However, you need to ensure that the parameters are not dropped when the login screen is displayed. You can do this by mapping the parameters to the clipboard and adding them to the login screen.
- Set the operator context in the SSO itself. As mentioned in reference 3, you can set the access group of the user in the SSO activity. This allows you to have different behaviors for different users.
- Update the "Starting activity to execute" for the Operator. As mentioned in reference 7, you can set the CaseID from the assertion token to the OperatorID page temporarily and update the "Starting activity to execute" to another activity that checks if the Case ID exists and then opens the assignment or shows the Desktop.
Remember to test these options thoroughly to ensure they meet your requirements.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
How to read Extra Parameter during Log In
SSO- user access to multiple applications
Based on the context, there are a few design options you could consider:
- Customize the SSO Authentication Service to call an activity that extracts the query parameters. This is mentioned in reference 2. However, you need to ensure that the parameters are not dropped when the login screen is displayed. You can do this by mapping the parameters to the clipboard and adding them to the login screen.
- Set the operator context in the SSO itself. As mentioned in reference 3, you can set the access group of the user in the SSO activity. This allows you to have different behaviors for different users.
- Update the "Starting activity to execute" for the Operator. As mentioned in reference 7, you can set the CaseID from the assertion token to the OperatorID page temporarily and update the "Starting activity to execute" to another activity that checks if the Case ID exists and then opens the assignment or shows the Desktop.
Remember to test these options thoroughly to ensure they meet your requirements.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
How to read Extra Parameter during Log In
SSO- user access to multiple applications
How to route a user directly to a specific work object instead on default screen - we are using SAML
Defining security information for an operator
--------------------------------------
@sivar1 @AdityaSethia @SumanKumar would you be able to provide some input?
Cox
US
@MarijeSchillern Thank you very much. I will check and respond back.
Cox
US
@MarijeSchillern we are able to achieve the desired functionality by following the below approach:
//
update the "Starting activity to execute" from "Data-Portal.ShowDesktop" to another where you can check if the Case ID exists in then open the assignment otherwise show Desktop.
//
However, these are existing users in production where they login usijng SSO link and go to user portal. The desired requirement is that the same existing user when logs in with SSO url with query parameters, we need to show work object if the query parameters has a case id. The issue is, Data-Portal.ShowDesktop is final activity, we cannot modify this activity to achieve different behaviour, so we created another activity and used it in the operator id. This worked. We could use this activity to conditionally route to showdesktop activity based on the query parameter but there are many operator ids and this solution requires modifying all the operator ids as the current implementation does not create operator id if id is already exists. So the goal is to minimize the impact to the existing operator ids.
Please advise!
Cox
US