root/resilient
1
0
Fork 0
Code Issues 3 Pull requests Projects 1 Releases 8 Packages Wiki Activity Actions

root/resilient#9 Passou a redireccionar login SAML2 com sucesso para o
All checks were successful
Release / release (push) Successful in 21m21s
Details

Browse source 
sucess-url, quando definido
This commit is contained in:
Orlando M Guerreiro 2025-06-12 15:00:19 +01:00
parent 7a69e6c491
commit 7cfc16e04d
1 changed files with 6 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

19
src/main/java/com/oguerreiro/resilient/security/saml2/Saml2AuthenticationHandler.java
View file

@ -162,19 +162,12 @@ public class Saml2AuthenticationHandler implements AuthenticationSuccessHandler,
userdetails.getAuthorities());
SecurityContextHolder.getContext().setAuthentication(newAuthentication);
// This is a sugar-code when in development environment.
if (isDevProfileActive()) {
// If this is a mock-idp, it can provide the parameter 'SAMLDevEnvironmentUrl'
// that gives the base URL to use. This is because in DEV mode usually the
// Angular side runs in localhost:42000 but server-side is in localhost:8080.
// Without this, SAMLv2 authentication would end up in error redirecting the user to
// localhost:8080 (NOT the client-side)
// In PROD we don't need this, because the app url is the same
String successUrl = resilientSaml2Properties.getSuccessUrl();
if (successUrl != null && !successUrl.isBlank()) {
response.sendRedirect(successUrl);
}
// Send to success URL, if configured
String successUrl = resilientSaml2Properties.getSuccessUrl();
if (successUrl != null && !successUrl.isBlank()) {
// This is mandatory in DEV environment. Optional in PROD because the app url is the same.
// Even so, I think its a good practice to define the success url
response.sendRedirect(successUrl);
}
}