11/2/2016 2:54:43 PM
(hardcoded at the moment)
|
11/2/2016 12:33:22 PM
<Extensions>
Some SP clients might be confused by using a standard SAML protocol tag
<Extensions> which is used for signed REDIRECT binding messages to
specify signing key ID. To enable the interoperability, generation of
the tag is disabled by default and can be enabled for individual
clients.
|
11/2/2016 5:46:06 AM
to POST binding, signature of SAML protocol message sent using
REDIRECT binding is contained in query parameters and not in the
message. This renders <dsig:KeyName> key ID hint unusable. This commit
adds <Extensions> element in SAML protocol message containing key ID so
that key ID is present in the SAML protocol message.
|
|
|
11/4/2016 6:05:35 AM
adapter
and
KEYCLOAK-1881 Extract httpclient configuration from AdapterConfig
|
|
|
|
|
10/24/2016 6:43:48 PM
and protocol message
Changes of SAML assertion creation/parsing that are required to allow
for validation of rotating realm key: signed SAML assertions and signed
SAML protocol message now contain signing key ID in XML <dsig:KeyName>
element.
|
11/1/2016 10:39:14 AM
in protocol messages
|
11/8/2016 4:37:00 AM
: Send 401 when no keycloak.json for EAP6/AS7 Adapter
|
