...
Redirect Crowd to another site login after successful user password reset
"Additional XSRF checks failed" error in logs when running behind a reverse proxy
If you encounter issues with resetting passwords (e.g. "Crowd cannot reset your password") or if you cannot access crowd's audit log, it's most likely that your being stopped by XSRF protections.
To resolve this, ensure that proxyName, proxyPort, and scheme directives have been added to crowd's server.xml. E.g.:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<Connector acceptCount="100"
connectionTimeout="20000"
disableUploadTimeout="true"
enableLookups="false"
maxHttpHeaderSize="8192"
maxThreads="150"
minSpareThreads="25"
port="8095"
redirectPort="8443"
useBodyEncodingForURI="true"
URIEncoding="UTF-8"
compression="on"
sendReasonPhrase="true"
compressableMimeType="text/html,text/xml,application/xml,text/plain,text/css,application/json,application/javascript,application/x-javascript"
proxyName="crowd.example.com" proxyPort="443" scheme="https"/> |
and then restart crowd.
Adding swap memory for smaller AWS instances (like t2.micro)
Apparently crowd doesn't need that much memory, but I have witnessed memory allocation errors (due to not enough memory) for servers/instances with <=1GB memory. Add swap space can alleviate this.
Please see Create and enable swap file on LInuxLinux for directions of adding swap to your AWS instance.
...