"XSRF check failed" exception occurs in some REST APIs after HTTPS is used

[lamella]

We are testing using crowd as the center to perform SSO login of jira, confluence and other systems, and using nginx for URL forwarding. Most of the pages can be accessed normally, but when we try to edit SSO in the crowd application, the page as a whole has an "XSRF check failed" exception.
We use docker to deploy crowd, jira and other systems. In the environment configuration of crowd, we set ATL_PROXY_NAME to 192.168.0.40 and ATL_PROXY_PORT to 443, but this does not seem to have any effect, but makes the default port 8095 unable to access normally up.
So, does anyone know what to do in this situation? I refer to crowd configuration tomcat to ssl mode, and replace the server.xml file mapping of tomcat, but they cannot be accessed normally.

[lamella]

This is the configuration of nginx

And this is the server.xml configuration in crowd's docker container

And this is the rest api where crowd has "XSRF check failed" exception