On 29.7.2015 16:37, Michael Gerber wrote:
The ClearAuthenticationCache command deletes the following data:
- Session cookies
- HTTP Authentication (e.g. Digest or Basic HTTP credentials)
- HTTPS Client Certificates (e.g. sites that use certificates or
But keycloak needs the session cookie, otherwise the user has to
relogin after each page reload.
Isn't the clientSecret anyway public if it is send in the
Yes, it is for JS clients. That's why it's better to
clients as "public" in keycloak admin console. In this case keycloak.js
will use client_id parameter instead of Authorization header. Can this
work for you?
Thing is, that currently AuthorizeClientUtil will likely automatically
send 401 if it found "Authorization: Negotiate ..." header even if you
have public client and you want to use client_id (I did not test it, but
guessing from looking at the code). So I've created the simple patch to
So if you do the steps like:
1) make your client as public
2) Apply my patch
will it help?
send REST requests authorized by "Authorization: Bearer" header with
accessToken. Not sure if IE doesn't again overwrite the header with
"Authorization: Negotiate". In this case REST request would fail. But
hopefully not... If you have opportunity to try it, it will be cool.
Am 29. Juli 2015 um 14:27 schrieb Bill Burke <bburke(a)redhat.com>:
> The trick you found earlier doesn't work?
> Also, what if in keycloak.js if kc.clientSecret is null? Just remove
> the client secret IMO. You shouldn't be exposing the client secret as
> it is now public to everybody in the world....
> On 7/29/2015 8:05 AM, Michael Gerber wrote:
>> I could find a solution for my IE problem.
>> IE overwrites the Authorization header in the XMLHttpRequest
>> (/protocol/openid-connect/token) with "Authorization: Negotiate".
>> To solve this problem, I added on the client the client_id
>> and client_secret to the form and changed the authorizeClient method, so
>> it checks first the form data instead of the authorization http header.
>> Have a look at my code:
>> Should I create a pull request for the changes or do you have a better
>> Am 22. Juli 2015 um 11:46 schrieb Marek Posolda <mposolda(a)redhat.com
>>> Hi Michael,
>>> No idea if there is other solution, I've never tried SPNEGO with
>>> Internet explorer TBH :(
>>> Could you please create JIRA for this?
>>> On 22.7.2015 10:07, Michael Gerber wrote:
>>>> Hi all
>>>> My kerberos configuration works fine with FireFox and Chrome, but it
>>>> does not work with IE.
>>>> It shows a prompt where the user has to enter a username and password.
>>>> I can successfully get an access code, but I can not get an access
>>>> token, because IE overwrites the Authorization header in the AJAX
>>>> request. (see
>>>> I can fix this by adding
>>>> above of
>>>> var req = new XMLHttpRequest();
>>>> approximately at the line 374 in the keycloack.js file.
>>>> Is there another solution for this problem?
>>>> keycloak-dev mailing list
>>>> keycloak-dev(a)lists.jboss.org <mailto:email@example.com>
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org <mailto:firstname.lastname@example.org>
> Bill Burke
> JBoss, a division of Red Hat
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org <mailto:email@example.com>
keycloak-dev mailing list