You can translate the question and the replies:

Unable to connect to vdp services with CSRF token validation errors

denodo 06:24:27.43 INFO ==> ** Starting Design Studio ** [SSO] 6320 [RMI TCP Connection(2)-] INFO 2024-04-10T06:24:35.307 [] - Starting DenodoSSOWebApplication v8.0.7 using Java 11.0.8 on designstudio-1 with PID 629 (/opt/denodo/resources/apache-tomcat/webapps/sso/WEB-INF/classes started by denodo in /opt/denodo/resources/apache-tomcat/bin) [SSO] 6332 [RMI TCP Connection(2)-] INFO 2024-04-10T06:24:35.319 [] - No active profile set, falling back to 1 default profile: "default" [SSO] 8932 [RMI TCP Connection(2)-] INFO 2024-04-10T06:24:37.919 [] - Started DenodoSSOWebApplication in 3.346 seconds (JVM running for 8.975) denodo 06:24:53.00 DEBUG ==> ** Waiting for PID 629 ** [DS] 849263 [https-jsse-nio2-9443-exec-2] ERROR 2024-04-10T06:38:38.250 [] - Access denied for https://denodo-domain:9445/denodo-design-studio/login?isWebLogin=false caused by Could not verify the provided CSRF token because no token was found to compare.
10-04-2024 03:11:59 -0400

1 Answer

Hi, This error “Could not verify the provided CSRF token because no token was found to compare.� suggests that the browser either can't create a secure cookie or is unable to access the cookie needed for login authorization. A possible cause would be not enabling the Sticky Sessions configuration in the Load Balancer. Also, please take into consideration that the default HTTPS port number for Denodo embedded web container is 9443 unless configured differently. Refer to the following documents, for further instructions: [- Prevent Load Balancers From Closing Connections of Data Catalog and Design Studio.]( [- HTTP Session Stickiness.]( Hope this helps!
Denodo Team
16-04-2024 02:10:28 -0400
You must sign in to add an answer. If you do not have an account, you can register here