title: Keycoak Realm Mixed clients (SAML + OIDC), SignOut redirect to another application's URL
body: <p>We have SAML and OIDC based clients configured in the same realm to achieve Single-Sign-On.
  One of the recent client is (Angular + spring-boot) application is using OIDC.</p>
  <p><strong>Given:</strong>
  User is logged in to let's say Application1 which uses SAML.
  User logs in to another Application2 (which uses angular , spring-boot, OIDC, JS adapter)</p>
  <p><strong>When:</strong>
  User logs out from angular app (Application2),</p>
  <p><strong>Then:</strong>
  keycloak sends HTTP 302 response with SAML logout URL and loads entirely different application i.e. APPLICATION1.</p>
  <p>Looks like keycloak is trying to perform Single-Sign-Out and that is creating the issue.</p>
  <p>Can you please help us find a way out?</p>
  <ul>
  <li>How to avoid being redirected to SAML app when logging off from another client.</li>
  <li>Can we still achieve Single-Sign-On with mixed client types?</li>
  <li>Can I make an AJAX logout call? Seems to be blocked by CORS. Weborigin is set to *</li>
  </ul>