Skip to main content
K
keviny
December 3, 2021
Question

Manipulate Response Going to IDP with Site

  • December 3, 2021
  • 8 replies
  • 0 views

Hello Appian Community,

We are facing an interesting issue with SAML SSO where we are trying to return the Site the user is trying to access in the IdP response.

The reason for this is we have an application with two sites in Appian. Based on user permissions they might have access to one or both sites. 

In the scenario they have access to two sites we want them to navigate to the site they click. The issue is Appian can only have one IdP per entityId specified in the MetaData so when the response is returned to the IdP they aren't sure which site it is the user wants to access.

Our hopeful solution is to have Appian return, in the response to the IdP, the site the user is trying to access so the IdP can redirect. Is there any possible Appian solution to edit the IdP response?

Thank You,

Kevin

8 replies

stefanhelzle0001
stefanhelzle0001
Brainy
December 3, 2021

Does this solve your problem?

docs.appian.com/.../Appian_Administration_Console.html

K
kevinyAuthor
December 3, 2021

Not quite. We've proposed this solution and the user only wants a single click to redirect to the correct site. Instead of a click to SSO and then another click to go to the specific site, but we appreciate your response.

stefanhelzle0001
stefanhelzle0001
Brainy
December 4, 2021

Sorry, I meant this: docs.appian.com/.../Appian_Administration_Console.html

K
kevinyAuthor
December 6, 2021

To clarify here.

The goal here is to see whether or not we can include additional properties (i.e. site requested) on the SAML Auth request from Appian that would allow the IdP to better handle generating the claims. As of now, we use “InResponseTo” which has been beneficial for redirecting to the correct Appian site. The issue is knowing which site the user is requesting when the SP request reaches the IdP.

 So the question is whether we can alter the “Appian’s SP request” rather than the “IdP Response” so we could potentially include the site requested.  

    Terms & ConditionsAccessibility statement