On 01/07/2013 12:44, Denis Signoretto wrote:
Hi,
I'm coming back working on Syncope after a while. I'm coming from Syncope 1.0.X
and taking confidence with new 1.1.2 release.
According to documentation [2], I have set secretKey at project creation time.
Buti t doesn't seams to work.
It's seams that on Syncope 1.1.X secretKey it's managed at build time [1]. I've
tried passing secretKey as a maven command line property
mvn clean package -Dbundles.directory=/opt/syncope/bundles
-Dlog.directory=/opt/syncope/log -DsecretKey=...
and seams to work as aspected.
It's correct or I'm missing something?
Hum, it smells like a bug: ${secretKey} in
core/src/main/resources/security.properties should get resolved during
project generation: I have opened SYNCOPE-398 for this.
Anyway, once such variable lies unresolved, passing a value in the way
you report above is definitely an option.
Alternatively, you can just edit
core/src/main/resources/security.properties and put the desired value there.
Regards.
[1]
https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments#RunSyncopeinrealenvironments-Buildanddeploy
[2]
https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+new+Syncope+project
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
