SpringSecurity 6.3.3 custom webfilter use example?
I had some trouble using spring webflux with spring security. Here is my version list:
Spring-security-oauth2-client to authenticate ourselves with a downstream service
I’m not even sure I’m knocking on the right door so bear with me on this. I have a service, that’s being called by another service (upstream) and calls a third service (downstream). My service provides auth mech X for the upstream, but should call downstream with oauth2 due to a change on that service.
The ‘/saml/logout’ call is not redirecting to the Asserting party for the Single Logout. Instead I’m getting a ‘404 Not Found’ error
I’m working on migrating my existing saml Single Sign On feature from the saml-extensions library to the new Saml 2.0 framework.
The ‘/saml/logout’ call is not redirecting to the Asserting party for the Single Logout. Instead I’m getting a ‘404 Not Found’ error
I’m working on migrating my existing saml Single Sign On feature from the saml-extensions library to the new Saml 2.0 framework.
Encoded password does not look like BCrypt Spring Security with OIDC
First things first, I want to tell that the “password” column in my db is 255 characters length, and that I persist it correctly to the db:
How to use a custom UsernamePasswordAuthenticationFilter with spring-security 6.3.1?
I am rebuilding an old Spring Boot application which was using old version of spring-boot and spring-security with java 8. I am currently using 3.3.2 for spring-boot and 6.3.1 for spring-security.
multiple identity providers with spring security
we are building a webapi for external clients. we want the clients to authenticate using their corp accounts. since each firm will have their own IdPs, we are looking at a system where the JWTs can have different iss
and aud
mutiple idenity providers with spring security
we are building a webapi for external clients. we want the clients to authenticate using their corp accounts. since each firm will have their own IdPs, we are looking at a system where the JWTs can have different iss
and aud
Why does Spring 5 give me 403/404 for the from login
I upgrading an app from Spring Security 3.2 to 5.8. Following Spring Security XML I get a 403 if I don’t have
What is the alternative way to get authenticationManagerBean() without WebSecurityConfigurer?
WebSecurityConfigurer already deprecrated