Awesome, thanks a million!
Pavel Maslov, MS
On Fri, Dec 28, 2018 at 12:16 PM Niko Köbler <niko(a)n-k.de> wrote:
As you can see, the bean definition ist Request-scoped.
This leads to a new bean instance for every request, and thus for each and
every user :)
Am 28.12.2018 um 11:46 schrieb Pavel Maslov <pavel.masloff(a)gmail.com>:
Excellent, this is exactly what I was looking for!
In your example does the *accessToken *injected field return a token for
each and every user respectively (not the same)?
Thank you very "many" (much) :))
Pavel Maslov, MS
On Fri, Dec 28, 2018 at 11:38 AM Niko Köbler <niko(a)n-k.de> wrote:
> Hi Pavel,
> that's quite easy (as most things with Spring Boot).
> You can get the AccessToken object through the HttpServletRequest,
> KeycloakPrincipal and KeycloakSecurityContext.
> In my projects, I do some bean definitions like here:
> Then, you can just inject the AccessToken or KeycloakSecurityContext
> where you want, like this:
> Instead of the AccessToken, you can also get the IdentityToken, of course.
> - Niko
> > Am 28.12.2018 um 11:22 schrieb Pavel Maslov <pavel.masloff(a)gmail.com>:
> > Hi, guys. Haven't been here for quite a while :)
> > I'm using the Springboot Keycloak adapter
> > (org.keycloak:keycloak-spring-boot-starter:4.6.0.Final) to secure my
> > API via bearer token . And it works! Cool.
> > Now, I would like to get the access token in my @RestController, or even
> > better some information about the user. Is it possible?
> > Thanks in advance.
> > Regards,
> > Pavel Maslov, MS
> >  https://github.com/maslick/barkoder
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-user