j_spring_security_check error

Confluence User - 30 May, 2024

I'm trying to update to update to 8.1.1 from 8.0.4 but I can't pass this error:

This site can’t be reached

The webpage at https://domain.com/jw/j_spring_security_check might be temporarily down or it may have moved permanently to a new web address.
ERR_FAILED

I tried updating the path for tomcat and the aspectjweaver jar to the latest one but it simple fail to allow me to sign in again.


What should I try?

Thanks!

server

3


30 May, 2024
confluenceUser
confluenceUser

Hi, Try this : 
Make the below changes in your spring-security.xml. Mention the login-processing-url="/j_spring_security_check"

<form-login login-processing-url="/j_spring_security_check" login-page="/login" default-target-url="/"
            authentication-failure-url="/login?error" username-parameter="username"
            password-parameter="password" />

try and error with various troubleshooting steps too: 

Check Application Logs

  • Examine the logs for detailed error messages. Focus on authentication-related errors.
  • Logs can typically be found in the catalina.out file or application-specific log files.

Verify Spring Security Configuration

  • Ensure your Spring Security configuration files (security-context.xml, WebSecurityConfig.java, etc.) are correctly set up.
  • For XML-based configuration, ensure the j_spring_security_check URL is properly mapped in the <http> block.

Hope this helps!

30 May, 2024
confluenceUser
confluenceUser

Sorry, but this solution doesn't solve my problem.


I'm running out of the box Joget, no modification, my joget running version 8.0.4 is running perfectly and doesn't have any of the files you mentioned. When trying to update to 8.1.1, which has a new Tomcat version and a new aspectjweaver updating from 1.9.7 to 1.9.22, the system fails in that call. Both versions are setup with the same files, just updating the necessary jar or directories and it simple fails.


I'm stuck because all the conf files that I could check matches the 8.0.4 version, but I'm probably missing something.

30 May, 2024
confluenceUser
confluenceUser

I found the problem... running it on Ubuntu my server.xml file had a different user and group from what it was expected. I just had to change file ownership to make it work.


Thanks!

RELATED QUESTIONS

Your answer


To answer a question you'll need an account.

Print