[
https://issues.apache.org/jira/browse/STONEHENGE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701214#action_12701214
]
Ben Dewey commented on STONEHENGE-13:
-------------------------------------
I think we should take a slightly different approach with this. I think we
should chagne the SetupActions and *.config files to use the trade/trade
credentials throughout. Thats what the PHP and WSAS sites are using.
> Synchronize the password in the database setup with the password in the order
> processor and business services is different
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: STONEHENGE-13
> URL: https://issues.apache.org/jira/browse/STONEHENGE-13
> Project: Stonehenge
> Issue Type: Improvement
> Environment: .NET setup_utilities for SQL Server 2008
> Reporter: Scott Golightly
> Assignee: Scott Golightly
> Priority: Minor
> Fix For: M1
>
> Attachments: Stonehenge-13.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> The setup script creates a database user with a password. The password for
> the user must be changed before the application can be run because the
> password is different than the passwords stored in the order processor and
> business services code. There is a documented workaround now to change the
> password in the database using the SQL Server management tools. I feel this
> step could be removed and the setup streamlined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
