Sender | Message | Time |
---|---|---|
19 May 2022 | ||
I believe you'll want to be using Spring Boot 2.7.0 to upgrade to the latest version of Spring Security. | 22:15:51 | |
20 May 2022 | ||
I saw that After those changes, how can I respond to a request inside from a ;SecurityContextRepository | 03:35:12 | |
* I saw that After those changes, how can I respond to a request inside from a | 03:36:21 | |
* I saw that After those changes, how can I respond to a request inside from a | 03:39:22 | |
* I saw that After those changes, how can I respond to a request inside from a | 03:41:17 | |
05:47:11 | ||
Thanks for you help! Based on your feedback, I’m going with keeping the user session active and implementing the features needed to make that work (such as destroying the session when the user changes their password). | 07:09:53 | |
* Hello! I would like to avoid leaving a form login session open after an OAuth2 authorization code ( And is there a way to make this work with stateless session management? I’ve toyed with So the chain would be:
rather than what's currently happening:
Any pointers would be much appreciated :). | 07:09:53 | |
* Hello! I would like to avoid leaving a form login session open after an OAuth2 authorization code ( And is there a way to make this work with stateless session management? I’ve toyed with So the chain would be:
rather than what's currently happening:
Any pointers would be much appreciated :). | 07:10:00 | |
I’ve accepted and upvoted your SO answer. | 07:10:00 | |
I can't use this because i'm using webclient instead of resttemplate. | 08:01:44 | |
In reply to @sjohnr-621e97856da0373984914e8a:gitter.imThank you very much. It helps! | 08:44:41 | |
13:27:18 | ||
I noticed that in February, the Keycloak team announced they are deprecating most Keycloak adapters, including Spring Security and Spring Boot adapters. So it means that keycloak-spring-security-adapter , which is also used by keycloak-spring-boot-starter , is being deprecated by the end of 2022. What are the best alternatives? To continue using newer versions of Keycloak with your own integration or move to other solutions, for example Spring Authorization Server? In the latter case, is it ready for use in production? Thanks in advance. | 13:27:19 | |
I've been using the standard oidc/OAuth spring security modules with keycloack without issues | 13:51:31 | |
14:03:56 | ||
Sorry about that, I didn't realize. Here's the same chapter using the reactive APIs https://docs.spring.io/spring-security/reference/reactive/oauth2/client/authorization-grants.html#_refreshing_an_access_token | 14:54:02 | |
And you can scroll down a bit or here's a link to the section on customizing WebClient: https://docs.spring.io/spring-security/reference/reactive/oauth2/client/authorization-grants.html#_customizing_the_webclient_2 | 14:55:43 | |
21 May 2022 | ||
22:03:42 | ||
Hi, I have a project where I don't explicitly create a bean for ReactiveJwtDecoder and instead make use of the default one provided by spring boot which uses the configuration I set in my properties file. Since I upgraded to the latest spring boot version (2.7.0) I noticed that in another class where I am using @Autowired ReactiveJwtDecoder, Intellij tells me that it can't find any bean for autowire. From what I could make sense of, in the new version the default bean seems to be lazily initialized by SupplierReactiveJwtDecoder. Everything still works as fine at runtime but I was wondering, does this change means that it is recommended to explicitly declare a bean for the ReactiveJwtDecoder instead of making use of the default one? | 22:03:43 | |
22:22:56 | ||
22:22:56 | ||
Redacted or Malformed Event | 22:23:33 | |
I always got "Bad Credential". Can some give me a solution? | 22:25:50 | |
22 May 2022 | ||
13:57:27 | ||
do you use the default spring login page or your custom one? | 13:57:29 | |
23 May 2022 | ||
Thanks for reply, It looks good :) | 06:59:03 | |
11:18:28 | ||
Hello is there a general spring room? | 11:18:40 | |
17:20:09 |