Gadget configuration consists of OAuth key, Shindig properties, and security token key. By default those configuration files are located at:
gatein/conf/gadgets for Tomcat.
standalone/configuration/gatein/gadgets for JBoss.
To use your customized configuration files, it is recommended that you replace default files in that location with yours.
It is possible to change the location by pointing
exo.conf.dir to another folder.
exo.conf.dir holds many configuration files besides gadgets, so take care that you have those files in the new folder.
Also note that the folder of gadgets files will be
In Tomcat: customize the variable
(see Customizing variables for how-to).
In JBoss: edit the property
standalone-exo-cluster.xml in cluster mode).
<property name="exo.conf.dir" value="/path/to/your/folder"/>
The security token key (
key.txt) is automatically generated by the server so you just need to acknowledge its location.
Next is more information about OAuth key and Shindig properties.
In eXo Platform, the OAuth gadgets use an OAuth key to authorize with external service providers.
There is always a default key defined in the
This key will be used in case the OAuth gadgets do not indicate a key.
It is strongly recommended that you create your own
by using the openssl tool and some commands as follows:
openssl req -newkey rsa:1024 -days 365 -nodes -x509 -keyout testkey.pem -out testkey.pem -subj '/CN=mytestkey' openssl pkcs8 -in testkey.pem -out oauthkey.pem -topk8 -nocrypt -outform PEM
Then, replace the default oauthkey.pem with yours.
Some Shindig features require online access which may lead to significant delay time at startup time.
Administrators can disable those features in the
Once the online features, for example analytics, are disabled, they will not be available in gadgets.