Outstanding issues

Broken History: The user using a browser is not being passed to the database. This is affecting all SASD Websites that connect to SQL Database that have the history mechanism enabled. History is not recording who is making changes to data. This has showstopper ramifications to timesheet application – possibly others. In addition it affects the plans application which uses ntGroups to control it's security (This was fixed in the past by Pedro/Evan, I’m not sure what they did. 1) Added application pool, 2) Added a trust account (spid) between website and database, 3???

Compatibility View Issue: Websites are being converted to https://xxx.saccounty.net (for example timesheet is now https://sasdtimesheetv2dev.saccounty.net/Timesheet_v2.aspx). Issues is saccounty.net is listed has the ‘Compatibility View’ flag set. This was needed to keep the old ASP applications running. Some asp.net applications will need to be fixed.
- Solution: I think newer applications should be moved to an HTTPS site that is not bound to .saccounty.net

Show All Content Button: After conversion, Regional San websites throw security based warning messeges like
- ‘Only secure content is displayed’ along with a button ‘Show all content’.
- ‘This page is accessing information that is not under it’s control. This poses a security risk. Do you want to continue’

There is an IE setting to loosen security, but I think the issue is there are some hardcoded references (for example <link rel=stylesheet type=text/css href='http://regionalsandev.saccounty.net/Requests/includes/requests.css'> ) which need to be changed to something like <link rel=stylesheet type=text/css href=../Requests/includes/requests.css'

Solution: Coding for each page must be performed, before we can switch from HTTP 2 HTTPS

SASD Maximo Conversion - F5 server will not convert the websites used by Maximo - because F5 doesn't do either ports or server names, maximo website is a server/port. (Uses IBM Server not IIS, nor Apache, etc)
- Solution: alternate HTTPS solution?

Solved issues

Login Window: Sasdapps-19 – when you access a site, you must provide credentials (I think this is fixed by adding https://*.saccounty.net to the Trusted sites list)
- 20190910 – Tina deployed a fix for this

Potential Issues for testing

integration with different databases/websites/directories need to be tested.
rest / etc - integration services potential errors
links coming and going to the website. (email, etc)

Notes from https://confluence.sacsewer.com/display/~wachdorfm/ITSEC-546

Lessons learned

8/22/2019 - it wont be 6 batches, I think it will be lots of small batches
8/22/2019 – Process
- Select batch for conversion
- Test websites
  1. New: As part of the test, do a f12 console view and get an idea of errors being triggered
- Tracey converts website to https
- Mark tests
  1. Consult f12 console view for clues
- Programmers test
  1. Consult f12 console view for clues