Andreas Kupries

Status report after a few days of working on implementing the thing: The main visualization of the necessary workflow is taken from http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0-cd-02_html_m50a2ba3e.gif The same is described at https://xacmlinfo.org/2013/06/28/how-saml2-single-logout-works/ The...

Managed a full logout with KC now. That said, after that the UI does a number of things I was unable to track, and then landed on > https://tagetarl:8005/auth/login?err=An%20error%20occurred%20logging%20in.%20Please%20try%20again. in...

Status report: SLO works for Keycloak and OKTA now. - The keyword is `detached signature` - Not handled by `crewjam/saml` on receiving responses :arrow_right: KC issue - Not generated by...

> General comment. There seems to be quite a number of debug logs. I tend towards higher amount of logging by default. > Our debug logs overall in Rancher are...

The security review has completed as ok and closed. I have the go ahead to merge. __This is deferred until 2.10 is open, i.e. 2.9 is released.__

Relevant flaky test: https://github.com/rancher/rancher/issues/42248

# Validation ## Root Cause A change request to support logging a User out of the session held by the configured external auth provider (EAP), and thus out of all...

Rebased code pushed

The vault is currently reached at https://volt.cap.explore.suse.dev/. How different is that from the custom domain ? Where would the domain be registered/made ? Is this possibly something for Chris Olstrom,...

Hi @lordcf Is it possible for you to retest with a newer release of kubecf ? There is kubecf 2.2.3 in CAP 2.0.1. Further, do I understand "deploy KubeCF on...