[Hawkular-dev] Tenant Id - Not Part of URL

Juraci Paixão Kröhling jpkroehling at redhat.com
Thu Apr 30 02:58:04 EDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/30/2015 08:23 AM, Thomas Heute wrote:
> Just a note to say that Account integration needs to happen sooner
> rather than later, this is blocker for the MVP due ... last week
> 
> Also let's make sure this is consistent. - All components need to
> support the same multitenancy model. We may also need to adapt it
> to various places where Hawkular will be used (with OpenShift,
> "standalone", with FeedHenry...) so would help if we can keep each
> service relatively dumb about the model and keep the logic in
> Account. - URL vs Header, I kinda lean toward header, but more
> importantly we need consistency so component leads need to agree on
> 1 way.

With that in mind, the individual components need not to worry on
whether the tenant information is coming from path or header, as
accounts is able to inject a Persona instance into your REST
service/managed bean via CDI.

As it is right now, Accounts decides on the Persona (tenant) based on
the data from the request already, and this might either be the
currently logged in user (from Keycloak) or an information from HTTP
header (for instance, if the user selected an "organization" on the
account switcher).

- - Juca.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVQdJ8AAoJECKM1e+fkPrXioIH+wSAGUIkykiIBaDY2Jxl1bQI
imVdRe/51g4ie+/t2bfMTdA5tV3SghNdXYiAG8vxUw8y0iZIwOh4/ZpXm2PdHyMo
FbTwfkGrl6YpVMFlcFV3xEJig4QQa3bVRykkbDNXawPIA3VLDkA70e6xx+ji/xfO
BO7++So1pfwMzTT5QCZOoBiAoETX7n1fMIK/Q/ZYuFb42mQGHvMwm3lXH5CZQIAN
18bk2KYIa4gB30YddB5JxY0wbj1Z3WpGRPTT6MWluMJ9+A2DtM7weN2bMqJKOfz8
0wYlewpzzoxB9Udubf5Hwl6ThwqF2VkgZgyfpsdGi5Me3s+KXx8ZqmlF5AysVEk=
=yLC/
-----END PGP SIGNATURE-----


More information about the hawkular-dev mailing list