OK, I'm able to reproduce it. It seems to work at first, but then start
failing once the server is rebooted (!!).
- Juca.
On 22.01.2016 22:56, John Mazzitelli 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