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

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

There is a work remaining to complete in order to resolve this issue - 
Providing required credentials (maximum three, minimum one) root level secret 
repository. I hope as an initial work, doing these in three ways - JMX, one 
time password file, command line. For JMX, I have already added MBean. I have 
to add a simple MBean to manage server - later can add remote JMX connector and 
more JMX functionality. For command line, I expected to use Jline [1], but 
there was some issue in windows with that. Therefore, I will provide more 
configurable options.

When, initiating synapse, if the deployment mode is 'production', check for 
Secret Manager's state, if it is already initialized or can be initiated (only 
if required credentials can be provided -For JMX, this is false - late start), 
synapse will be started immediately. Otherwise, using JMX, it is needed to 
manually initiate the secret manager and then starts the synapse. 

[1] http://jline.sourceforge.net/

Thanks 
Indika 

> Securing password in the datasource definition 
> -----------------------------------------------
>
>                 Key: SYNAPSE-376
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-376
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: indika priyantha kumara
>            Assignee: indika priyantha kumara
>             Fix For: FUTURE
>
>
> Currently ,passwords in the datasource definition are in clear text format. 
> (In synapse.properties). Those have to be encrypted. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to