We are using keycloak 1.9.2 final version. The token would have got expired by now but it was valid when the api call was fired. Do you mean client keys set in keycloak.json? Regards, Ganga Lakshmanasamy On Sep 21, 2016 2:28 PM, "Stian Thorgersen" <sthorger(a)redhat.com&gt; wrote: > What version? Is the realm keys configured correctly? Is the token still > valid? > > On 21 September 2016 at 06:25, Ganga Lakshmanasamy <lganga14(a)gmail.com&gt; > wrote: > >> Hi, >> >> We are getting the "NOT_ATTEMPTED: bearer only" error while trying to >> access our backend rest service which has access type as bearer only from >> our public angular js based client. >> We are setting the "Authorization" header in our request but looks like >> the adapter is not able to recognize the header with the bearer token. >> >> Please help us resolving the issue. >> >> *Note*: We are able to invoke the rest services with same bearer token >> from other rest clients like post man and advanced rest client for chrome. >> The issue comes up only when we try from our angular js code. >> >> Regards, >> Ganga Lakshmanasamy >> >> _______________________________________________ >> keycloak-user mailing list >> keycloak-user(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/keycloak-user >> > >