[
https://issues.apache.org/jira/browse/STONEHENGE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775132#action_12775132
]
Pablo Mariano Cibraro commented on STONEHENGE-15:
-------------------------------------------------
Yes, that's correct. I think there is another bug in there, as the SQLHelper is
only building connection strings valid for SQL server and MySQL should also be
supported. We should store the whole connection string in the ConnectionString
section, there is no need to build the connection string dynamically as the
application is doing now.
> Protect connection strings in Business Services and Order Processor solutions
> -----------------------------------------------------------------------------
>
> Key: STONEHENGE-15
> URL: https://issues.apache.org/jira/browse/STONEHENGE-15
> Project: Stonehenge
> Issue Type: Improvement
> Components: DOTNET_BS, DOTNET_OPS
> Environment: .NET trunk
> Reporter: Scott Golightly
> Assignee: Scott Golightly
> Priority: Minor
> Fix For: M2
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The database connection strings are listed in plain text in the configuration
> files. .NET provides the means to encrypt the connection strings and
> automatically decrypt the values before using it. Encrypting the connection
> string is a best practice to protect the database login information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
