Error failed parsing SAML config

@Anthony

Well… Something good happened.
I had an idea after looking in the log files that the response of ES to Keycloak may have been incorrect.

So I start looking into keycloak. I was able to rid of error “500” and then received error “400”.
Assuming I could be on the right path to figuring this out.

After you mentioned about enabling logs this actually lead me to this error was.

/_opendistro/_security /saml/acs 400

Inwhich lead me here.

https://github.com/nextcloud/user_saml/issues/222#issuecomment-402542562

By enabling this button ( Red Box) it worked.

To sum it up.
The Order needed to be corrected under Auth section in config.yml file.
Proper URL in the SAML section of config.yml file need to be adjusted.
“change the challenge flag in basic auth from true to false”
Adding logger.token.name & logger.token.level to log4j2.properties file to resolve errors.
Keycloak need adjusting in the Mapper section of the “Client”.

@Anthony Thank you for you time and patients.

2 Likes