[SAML] Absolute path not working for metadata and keystore files
Affected version : Squash-tm 6.0.0 and 6.0.1 with security-saml 6.0.0
Steps to reproduce
- Install security-saml-6.0.0 plugin
- Write absolute path for IDP metadata, SP metadata and keystore with two "//" after "file:" as told in file's comment :
saml.idp.metadata.url = file://opt/squash-tm/conf/saml/FederationMetadata.xml
#The url or path where the SP metadata can be found. Allows the same formats than idp.metadata.url
saml.sp.metadata.url = file://opt/squash-tm/conf/saml/sp.xml
#The url of path where the keystore can be found. Only file:// or relative path are allowed.
saml.keystore.url = file://opt/squash-tm/conf/saml/keystore.jks
- Make other saml configurations to allow the plugin to work correctly
- Restart squash-tm
- Squash-tm is on ERROR and is unavailable :
Caused by: org.opensaml.saml2.metadata.provider.MetadataProviderException: Resource /squash-tm/conf/saml/FederationMetadata.xml does not exist.
- Add a third "/" to Metadata.xml absolute path :
saml.idp.metadata.url = file:///opt/squash-tm/conf/saml/FederationMetadata.xml
- Restart squash-tm, same error but with sp metadata file, add a third "/" to absolute path
- Restart squash-tm, same error but with keystore file, add a third "/" to absolute path
- Restart squash-tm, the error is not present anymore.
Use list
Expected result
Squash-tm can find the file with its absolute path configuration as told in the configuration file.
Observed behaviour
Squash-tm don't find it unless I add a third "/". This problem occured on 3 squash-tm installations (v6.0.0 and 6.0.1) and I haven't had a correct behavior with squash-tm 6.0.X yet. Exemple of squash-tm log with the error :