Anuj, Mazz,
On 23 Jan 2016, at 16:19, John Mazzitelli wrote:
Juca - can you take a look and tell me if its a problem in
accounts/keycloak? Based on my testing I think that's where the
problem lies, but I'm not 100% sure.
Does this work (for a previously created token):
curl -H 'Accept: application/json' -i -u
b3063b1f-640b-4853-81df-47257c01e63e:94edc711ef80c592cb417bfffd9bc496
http://localhost:8080/hawkular/accounts/personas/current
?
( from
http://www.hawkular.org/blog/2015/12/16/hawkular-1.0.0.Alpha8-released.html
)
Just create yourself a token and configure the agent to use it rather
than username/password and you should be able replicate the problem.
----- Forwarded Message -----
From: "Anuj Garg" <anuj1708(a)gmail.com>
To: "John Mazzitelli" <mazz(a)redhat.com>, "Discussions around
Hawkular
development" <hawkular-dev(a)lists.jboss.org>
Sent: Friday, January 22, 2016 10:03:12 PM
Subject: Re: [Hawkular-dev] agent cannot use security token
It happened to me too yesterday but i was thinking might be I am not
properly using the tokens coz I am new to it.
But was following the same procedure.
On 23 Jan 2016 3:26 am, "John Mazzitelli" <mazz(a)redhat.com> wrote:
> I just tried installing the agent to use securityKey/securitySecret
> rather
> than username/password and it failed to authenticate with the server.
> If I
> use username/password, it works fine.
>
> It isn't anything with the agent that seems to be the problem because
> during my testing, I attached to the agent with my debugger and right
> before I sent the auth message to
>
>
http://127.0.0.1:8080/hawkular/accounts/personas/current
>
> I change the value of the key/secret to "jdoe" and "password" and
it
> works. So there is something on the server-side that doesn't like the
> agent
> passing in the token credentials.
>
> Can I ask if anyone else sees the same thing? It's easy to test:
>
> 1) in the UI, create yourself a new token
> 2) in standalone.xml's <storage-adapter> element, change the
> "username"
> attribute name to be called "securityKey" and set its value to your
> new
> token's key and change the "password" attribute name to be called
> "securitySecret" and set its value to your new token's secret.
> 3) start the agent back up again
>
> It should work, but doesn't for me. I tried it with two different
> token
> key/secret pairs, failed both times.
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey,
Charlie Peters