OK so everything works but you sometimes see a stack trace. The stack
trace is coming from the keycloak auth adapter. As long as everything else
still works, I'd be inclined to either ignore it or report it to keycloak.
Yes, you right.
Thanks again for all information.
On Thu, Aug 13, 2015 at 9:24 AM, Eric Wittmann <eric.wittmann(a)redhat.com>
wrote:
OK so everything works but you sometimes see a stack trace. The
stack
trace is coming from the keycloak auth adapter. As long as everything else
still works, I'd be inclined to either ignore it or report it to keycloak.
Periodic calls to
http://localhost:8080/apimanui/rest/tokenRefresh are
expected. This is done to obtain a new auth token that can be used to make
authenticated calls to the API Manager REST layer (from the UI). The auth
token issued by keycloak expires after 2 minutes.
-Eric
On 8/13/2015 8:12 AM, Helio Frota wrote:
> In all these cases the UI kept working OK?
>
> Yes.
>
> Did you ever get any sort of failure in the UI?
>
> No.
>
> Example: missing data, page load failure, etc?
>
> No. nothing, I don't remember if i clicked on some button or link , or
> just the stack trace arise by doing nothing.
>
> Trying to catch this again ( i have no idea how, but trying )
>
> For now, I noticed that from time to time this is executed:
>
> GET
http://localhost:8080/apimanui/rest/tokenRefresh
> 200 OK
>
> apiman [9:04:28 AM]>> Bearer token successfully refreshed: {
> "token": "eyJhbG ... long token here",
> "refreshPeriod": 240
> }
>
>
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/apiman-user
>
>