Probably a bug :) The UI call the REST endpoint, so, it should be
possible to reproduce the issue only with REST calls. If you are able to
reproduce it, let me know and I'll add a test/fix.
- Juca.
On 21.03.2016 09:45, Anuj Garg wrote:
Thanks
But still the doubt remain is why token created with
/secret-store/v1/tokens/create is allowing to do so.
On 21 Mar 2016 1:55 pm, "Juraci Paixão Kröhling" <jpkroehling(a)redhat.com
<mailto:jpkroehling@redhat.com>> wrote:
I'm not sure I got what the problem is, but a token is always related to
a persona, be it the real user, be it an organization. You can't set a
Hawkular-Persona on a request with tokens, as the token itself stores
the "Hawkular-Persona" used when the token was created (defaults to the
actual user). So, if you want to have multiple personas on the android
client, you have to have multiple tokens stored locally, one for each
persona.
- Juca.
On 17.03.2016 19:40, Anuj Garg wrote:
> I was working on fetching data for different personas. At that
time I am
> facing that key/secret pair generated by
/secret-store/v1/tokens/create
> is being able to respond according to Hawkular-Persona provided
in the
> header.
> But One generated by "Create Token" on token page is not able to
work
> that way. I have tried only on resources till yet though.
>
http://pastebin.com/Rp9idM7s
> I am providing Persona of created org which should have returned
empty
> list but proving the resource URLs which are present in first
Persona.
>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org <mailto:hawkular-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hawkular-dev