-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/08/2015 08:17 AM, Heiko Braun wrote:
Maybe you'll find that keycloak only addresses part of the
requirements. This will impact the question wether or not to make
it a technological constraint.
Right, hence the question about the concrete use case you have in mind
:-) What kind of non-HTTP communication do you anticipate?
Note that even if Keycloak itself doesn't provides an adapter for
non-HTTP authentication, we could build one ourselves that takes the
authentication data from the "request" (or client) and does the HTTP
request to Keycloak server on its behalf.
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU2GqaAAoJECKM1e+fkPrXLmgH/jQwlnF1J2CZHOsFuE1FvjZS
NhWFNldNLa91pgbMuvncEKgKmRpKynRlfMsWQBD1RqrrSAivl3XUrNBR9m/W6EIL
SRnKSevISKXscJg90VVJnzD/tJsMVXDBS22HSOP7u6ENqZfdOCgUv3C6j5fgsLVS
cRfxG/yj6dZ66ueYmtBZ/wcrIzhSjKPXW/FW/1woR+i8pp2Q4yOX6TFcQ27/uO5q
IelQrjJqYaSnZtKEgVSF7QtUlrz+Cu4m4GnYr41OxuY2LQlX59PutJvS5UGipHJN
BY1G8EuAoZNWm1wirOhwl9N43+F8xW/gUqVluinwh7Ax0WMYAgiX5shcn/YO2Pc=
=5fau
-----END PGP SIGNATURE-----