A note about Jetty <Property/> elements sourced from conf/idp.properties
Tom Zeller
tzeller at dragonacea.biz
Wed May 7 21:40:16 EDT 2014
>>I was also hoping for container keystore paths and passwords to be in
>>idp.properties, but right now they would be in jetty-base/start.d,
>>which I do not like much.
>
> Unless we're bundling Jetty, which is no longer in the immediate plans, it
> doesn't really matter. We can't limit containers to just Jetty in practice
> (even if we didn't support Tomcat, people would still use it) and so
> targeting Jetty specific approaches doesn't really help that much anyway.
Right, agree.
More notes :
It looks like neither Tomcat nor Jetty can read property files at
arbitrary paths. The container will need the keystore password and
path, and since the keystore path is relative to idp.home it is user
configurable, which I was hoping to restrict/contain to
idp.properties.
Tomcat does support property replacement via catalina.properties, but
unlike the XML configuration files which support property replacement
from system properties, a property like
keystore.path=${idp.home}/creds/idp.jks in catalina.properties will
not be replaced properly even if idp.home is a system property, AFAICT
[1].
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=50677
More information about the dev
mailing list