[rhq.metrics] Keycloak vs. external client requests
Heiko W.Rupp
hrupp at redhat.com
Fri Nov 21 17:09:36 UTC 2014
> Am 21.11.2014 um 17:58 schrieb Juraci Paixão Kröhling <jpkroehling at redhat.com>:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 11/21/2014 05:39 PM, Heiko W.Rupp wrote:
>>
>> How often needs the access token being refreshed? If that is valid
>> for 1h or 1d, then I think this means "no overhead".
>
> It's configurable. Right now, this setting is per realm and is set to
> 5 minutes. Part of the discussion on the keycloak-user is to make this
> setting as per app or per OAuth client. Realm, in our case, is a
> tenant/user.
Sounds good.
>
> For code that we control, this is indeed OK. But I'm also thinking
> about custom collectors, built as shell scripts by the end user.
Lets get that flying for java+KC and then continue from there.
A shell script could (theoretically) store the refresh-token in an ENV var
Cool, thanks for looking into that.
Heiko
More information about the rhq-devel
mailing list