[Hawkular-dev] Ambiguity in behaviour of token generated by token page in web UI
Juraci Paixão Kröhling
jpkroehling at redhat.com
Mon Mar 21 04:25:20 EDT 2016
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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
More information about the hawkular-dev
mailing list