20191002 ITSec-546 - History Issue Review
Date
Attendees
Agenda/Notes
timesheet dev - works, but the user identity is not being passed to sql server. (To make this work we had to give security to the spid account)
timesheet qa - works, but user identity is not being passed to sql server.
I took the web.config in timesheet production, and then copied to development, and adjusted it to point to sasdddb1.staff (and other related databses) Result is annoymous user error.
I took the web.config in timesheet production, and then copied to qa, and then adjusted it to point to sasdddb1.staff_test (and other related databases) Result is it works, but history records user as dbo.
RUFFT testing (10/3/2019 ~3:00pm)
| Dev | Test | Prod | |
|---|---|---|---|
| Clerical | Anonymous user error | prompts for credentials | prompts for credentials |
| Timesheet | Anonymous user error | prompts for credentials | prompts for credentials |
Wachdorfm Testing (10/4/2019 7:22am)
| Dev | Test | Prod | |
|---|---|---|---|
| Clerical | boots | boots | boots |
| Timesheet | boots | boots | boots |
Summary
- The username() on SQL Server is not getting the person connecting to IIS. On any website on sasddiis1
- It seems like I the HTTP 2 HTTPS project did do something to the web.config file, because a simple freshen the file from production doesn't seem to be working.
Started a second conversation - SASD Websites and making them work with browsers other than IE11