Bug 794446 (JBEPP-1486)

Summary: Property names for key.txt and oauthkey.pem are not correct in the $JBOSS_HOME/server/<server-profile>/conf/gatein/configuration.properties file
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: bkramer <bkramer>
Component: unspecifiedAssignee: mark yarborough <myarboro>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0.GACC: epp-bugs
Target Milestone: ---   
Target Release: 5.2.x   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1486
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bkramer 2012-01-24 15:59:58 UTC 
project_key: JBEPP

Location of key.txt and oauthkey.pem files is defined in $JBOSS_HOME/server/<server-profile>/conf/gatein/configuration.properties file as gatein.gadgets.securitytokenkeyfile and gatein.gadgets.signingkeyfile while ExoContainerConfig.java file [1] is trying to get the following: gatein.gadgets.securityTokenKeyFile and gatein.gadgets.signingKeyFile. So, currently, when running the default installation of EPP 5.2 the following is logged in the log file:

WARN  [org.exoplatform.portal.gadget.core.ExoContainerConfig] (main) The gadgets token key is not configured. The default key.txt file in /bin will be used
...
WARN  [org.exoplatform.portal.gadget.core.ExoContainerConfig] (main) The gadgets signing key is not configured. The default oauthkey.pem file in /bin will be used

The following JIRA [2], partially fixed above issue [3].

[1] http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5_2_0_GA/gadgets/core/src/main/java/org/exoplatform/portal/gadget/core/ExoContainerConfig.java
[2] https://issues.jboss.org/browse/GTNPORTAL-2175
[3] https://source.jboss.org/changelog/GateIn?cs=7760