On 04/16/2016 10:06 AM, Bill Burke wrote:
I don't see any blockers here. If you want to log a few jiras,
we'll
get to the rest in Keycloak 2.0 (RH SSO 7.1). We will not be supporting
Artifact binding unless a critical mass of customers ask for it. I also
do not see us supporting ACSI either unless asked for either.
I'm not asking for KC to support ACSI or Artifact. Rather I was trying
to clarify SAML behavior when various attributes are present in the
AuthnRequest.
--
John