I have the same bug as already temporally fixed #1400 for the old 1.x version. When a client (noticed Firefox, Chrome, Edge and Word in the logs) sends an OPTIONS request, SSP throws an unhanded Exception.

There was an temp fix ( a7600ce ) for the 1.x version. As I see in the sources for the 2.x there wasn't an check until the commit e895170 but there was added an error report SSOPARAMS so I have now errors in the log files again.

Should it be an solution to add again the first approach with with sending back an header 405 ? Or what is the idea behind the "SSOPARAMS" error ?