[Apiman-user] Token is not active.

[Marc Savy]

I think this may pertain to the Keycloak OAuth2 token. In which case, I
provided Fadi with a version containing additional logging to see if we
could track the issue down.

It's not an issue I've ever been able to replicate, and we don't fiddle
with the token data in any way, so I don't really see how we could
affect things.

My only suggestions are to ensure that time is accurate on all of the
systems (NTP, Chronyd, etc), and I believe this has already been done.

On 10/08/2015 18:00, Eric Wittmann wrote:
> How often does this occur?  What is the result?
>
> I assume this is triggering a re-login in the UI?
>
> There is no caching on the apiman side.  However the tokens issued by
> keycloak to the apiman UI do have an expiration.  You could try logging
> into the keycloak auth admin UI and increasing the lifespan of the tokens.
>
> Any more details you can provide would be great.
>
> -Eric
>
> On 8/10/2015 8:56 AM, Fadi Abdin wrote:
>> I keep getting occasional "Token is not active." on they keycloak side
>> occasionally . its really frustrating , i cant figure out what could
>> cause this to happen. everything seems correct.
>>
>> Is there caching between API Man and Keycloak i can turn off ?  Have
>> anyone seeen this behavior ?
>>
>> Thanks,
>> Fadi
>> Express.com
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>