[ 
https://issues.apache.org/jira/browse/SYNAPSE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004049#comment-13004049
 ] 

indika priyantha kumara commented on SYNAPSE-735:
-------------------------------------------------

Asela ... It looks good to me... 

Minor changes - All tag names should be started with a simple case (Synapse 
convention)

<svns2: Property name="location" >/home/asela/test.txt</Property>  may need to 
be changed into <svns2:property name="location"  value="/home/asela/test.txt"/> 

I hope 'password' tags ( actually 'secureVaultAlias' attributes) are defined in 
the places where the actual passwords are given (e.g dblookup mediator 
configuration)

We have to define a new XML - securevault.xml ... and move secret manager 
configuration into the secret manager based password provider. Please use 
'secret' instead of password in the API as we may use this in other contexts as 
well.


Thanks,

Indika

> imporve password manager XML syntax which is defined in configuration files - 
> secure vault
> ------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-735
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-735
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1
>            Reporter: asela pathberiya
>             Fix For: FUTURE
>
>
> Xml syntax which must be configured for securing the passwords in xml files 
> some thing like follows
> <passwordManager>
>       <protectedTokens>AdminUser.Password</protectedTokens>
>       <passwordProvider>org.apache.synpaseTestProvider</passwordProvider>
> </passwordManager>
> It is better to rework to improve this xml syntax with namespace quilfied..

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to