Author: hiranya Date: Mon Jul 6 23:02:10 2009 New Revision: 40905 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=40905
Log: Minor modifications to the secure vault docs Modified: branches/esb/java/2.1/product/docs/xdoc/securing_secret_information.xml Modified: branches/esb/java/2.1/product/docs/xdoc/securing_secret_information.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/2.1/product/docs/xdoc/securing_secret_information.xml?rev=40905&r1=40904&r2=40905&view=diff ============================================================================== --- branches/esb/java/2.1/product/docs/xdoc/securing_secret_information.xml (original) +++ branches/esb/java/2.1/product/docs/xdoc/securing_secret_information.xml Mon Jul 6 23:02:10 2009 @@ -81,15 +81,15 @@ <p>All secrets are managed using the Secret Manager. Secret Manager can keep any number of secret repositories. Those are arranged in a cascading manner. All secrets are stored in one place - secret repositories. Secrets can be accessed by -providing aliases for them (no need to put encrypted value in inline in -application configurations). Key Stores needed for Secret Manager and secret +providing aliases for them (no need to put encrypted values inline in +application configurations). Key stores required by the Secret Manager and secret repositories are configurable. It can be done through the 'secret-conf.properties'. Currently, there is only one secret -repository and it is FileBaseSecretRepository. It uses cipher-text.properties +repository and it is called the FileBaseSecretRepository. It uses cipher-text.properties to keep secrets. It keeps aliases vs. its actual secret in encrypted format (encrypted by a key in keystore)</p> -<p><strong>Example </strong></p> +<p><strong>Example</strong></p> <p><strong>secret-conf.properties</strong></p> <pre>############################################################################ @@ -255,9 +255,9 @@ SecretInformation secretInformation = SecretInformationFactory.createSecretInformation(secretProvider, aliasPassword, passwordPrompt); String actualPassword = secretInformation.getResolvedSecret();</pre> -<p>Now you can pass either an actualPassword or secretProvider or -secretInformation to the code location that uses pasword. But if the code that -performs secret resolution can not be accessed. For example, when using a configuration +<p>Now you can pass either an actual password or a SecretProvider or +SecretInformation to the code location that uses the password. But if the code that +performs secret resolution can not be accessed, for example, when using a configuration such as follows - you cannot pass resolved password directly.</p> <pre> <datasource> _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
