You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to setup Lavagna with hsqldb but I when I click on "activate" at the end of the configuration steps it does nothing and prints "wrong csrf".
Server is listening at 0.0.0.0/0.0.0.0:8080
15:37:15.930 [main] INFO io.lavagna.common.LavagnaEnvironment - For property datasource.dialect, the value is: HSQLDB
15:37:15.935 [main] INFO io.lavagna.common.LavagnaEnvironment - For property datasource.url, the value is: jdbc:hsqldb:file:lavagna
15:37:15.935 [main] INFO io.lavagna.common.LavagnaEnvironment - For property datasource.username, the value is: user
15:37:15.936 [main] INFO io.lavagna.common.LavagnaEnvironment - For property spring.profiles.active, the value is: prod
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/user/AppData/Local/Temp/jetty-0_0_0_0-8080-lavagna-jetty-console_war-_-any-1103144440992649848/webapp/WEB-INF/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/D:/user/Documents/myApps/lavagna-1.1.9-distribution/lavagna-1.1.9/lavagna/lavagna-jetty-console.war!/WEB-INF/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
15:37:44.362 [qtp1818402158-14] INFO io.lavagna.web.security.CSFRFilter - wrong csrf
15:44:26.238 [qtp1818402158-25] INFO io.lavagna.web.security.CSFRFilter - wrong csrf
15:44:27.695 [qtp1818402158-37] INFO io.lavagna.web.security.CSFRFilter - wrong csrf
The text was updated successfully, but these errors were encountered:
I tried to setup Lavagna with hsqldb but I when I click on "activate" at the end of the configuration steps it does nothing and prints "wrong csrf".
The text was updated successfully, but these errors were encountered: