Principal about spring-addons

[arnonuem]

Ok i just found the solution to this. This repo could need some more documentation :D
In my case instead of using:

mockAuthentication(UsernamePasswordAuthenticationToken::class.java)

i had to just modify it to

val details = AppUserJwtAuthConverter.AppUserData("[email protected]", "fn", "Full", "Name")
mockAuthentication(UsernamePasswordAuthenticationToken::class.java).details(details)

And now the converter is also respected :)
Thanks a lot for that great repo. And please update your documentation in regards to the builder pattern with some more examples ;)

[ch4mpy]

Did you have a look at @WithMockAuthentication javadoc?

If the actual Authentication impl type is of no importance (because you're only doing role-based security for instance), something like @WithMockAuthentication(name = "Ch4mpy", authorities = { "ROLE_TESTER", "ROLE_AUTHOR" }) should be just enough.

For UsernamePasswordAuthenticationToken, isn't Spring's @WithMockUser more convenient to use ?

I'm not sure I understood your use-case: UsernamePasswordAuthenticationToken really is bad Authentication impl when parsing a JWT. I'd suggest you to use Spring's JwtAuthenticationToken, Keycloak's KeycloakAuthenticationToken, my OidcIdAuthenticationToken or an implementation of your own better targeted at your specific OAuth2 impl (not so complicated actually)

[arnonuem]

Hi, thanks for your insights. Actually this is not my project and i have to take what is there. So i am a bit stuck on that. But now all works nice an smooth. I gave you also a credit on stackoverflow :) 17. Feb. 2021, 03:29 von [email protected]:

…

Did you have a look at > @WithMockAuthentication> javadoc? If the actual > Authentication> impl type is of no importance (because you're only doing role-based security for instance), something like > @WithMockAuthentication(name = "Ch4mpy", authorities = { "ROLE_TESTER", "ROLE_AUTHOR" })> should be just enough. For > UsernamePasswordAuthenticationToken> , isn't Spring's > @WithMockUser> more convenient to use ? I'm not sure I understood your use-case: > UsernamePasswordAuthenticationToken> really is bad > Authentication> impl when parsing a > JWT> . I'd suggest you to use Spring's > JwtAuthenticationToken> , Keycloak's > KeycloakAuthenticationToken> , my > OidcIdAuthenticationToken> or an implementation of your own (not so complicated actually) — You are receiving this because you authored the thread. Reply to this email directly, > view it on GitHub <#17 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ADYZWE5P73JB753L7JXMJ5LS7MSWZANCNFSM4XWOEZGA>> .