Closed valentingoebel closed 6 years ago
Yes, as a new user of this plugin I tripped over this left right and center. It seemed to me you almost needed all of the config or else.
So as a simple starter, I was going to add a comment in the doco to that effect - i.e. all config must be present.
But also looking at the init processing the config there are things that could definitely be done to assist developers with configuration issues - e.g. log messages.
When I tried to add a new property "saml.metadata.timeout". I realised that the plugin doesn't actually load the default configuration.
// SpringSecurityUtils.loadSecondaryConfig 'DefaultSamlSecurityConfig'
If we migrate the default configuration to plugin.yml I hope we will see less crashes.
Ok I can confirm now that this has worked with autoCreate. I will create a PR soon.
Closing due to merging of PR.
Failing to adhere to the expected configuration format causes "byzantine" error messages that are very hard to understand.
As an example I've taken out this snippet from the application.yml
The cause of the error is that providers should be specified as a map, not a list but that is not obvious from the actual error message. It just says doCall wasn't found.
The application.yml should look like this. (no dash)
I'm sure there are more properties than just
providers
that also fail in non obvious ways when configured incorrectly.