Mike.Sheen wrote:SBarnes wrote:Has something changed in the encryption sequence since the first script was put together as that would explain why gibberish was being given for the user name?
- Code: Select all
UPDATE HR_Staff SET Password = '60A889064BAD474508723B9200184D09',
PasswordLastChangedDateTime = '2014-05-28 11:20:48.000',
LastSavedDateTime = '2014-05-28 11:20:48.000',
SQLLogin = '6B4A7C2B2E902402268692E8932CDB50',
SQLPassword = '1C57594FC45BBF79E1CB63D5452D4EE364CB73ED467F7C8C',
ReportSQLLogin = '887BFFE23AB10B3C5412655265278A11',
ReportSQLPassword = '1C57594FC45BBF79E1CB63D5452D4EE364CB73ED467F7C8C'
GO
Are you saying the above doesn't work for you? Because it works for me. I've just copy-pasted that script and run it against a 7.2.1 database and I could login fine.
To answer the question - no, we've not changed anything with regards to the encryption.
SELECT distinct [SQLLogin],[SQLPassword],[ReportSQLLogin],[ReportSQLPassword]
FROM [JiwaDemo].[dbo].[HR_Staff]
SQLLogin: 0E6019A460702D275F5CEC20300C0C43
SQLPassword: 12D663653B142E02AB7C1B29D4C4604693FF497BCECF23C1
ReportSQLLogin: 68B4E49B9080B8D8546F113D97CF5303
ReportSQLPassword: 12D663653B142E02AB7C1B29D4C4604693FF497BCECF23C1
pricerc wrote:actually,
- Code: Select all
SELECT distinct [SQLLogin],[SQLPassword],[ReportSQLLogin],[ReportSQLPassword]
FROM [JiwaDemo].[dbo].[HR_Staff]
returns
- Code: Select all
SQLLogin: 0E6019A460702D275F5CEC20300C0C43
SQLPassword: 12D663653B142E02AB7C1B29D4C4604693FF497BCECF23C1
ReportSQLLogin: 68B4E49B9080B8D8546F113D97CF5303
ReportSQLPassword: 12D663653B142E02AB7C1B29D4C4604693FF497BCECF23C1
on my dev vm.
edit 1: but then I can't remember what username/password I specified when setting it up.
edit 2: doubled back and checked - It's JiwaUser/JiwaFinancials123.
SQLLoginLastSavedDateTime = '2014-05-28 11:20:48.000',
ReportsLoginLastSavedDateTime = '2014-05-28 11:20:48.000'
Return to Technical and or Programming
Users browsing this forum: No registered users and 4 guests