Project

General

Profile

Actions

Change Request #61

closed
DL DL

Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.

Change Request #61: Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.

Added by David Leedom 2 months ago. Updated 2 months ago.

Status:
Completed
Priority:
Normal
Assignee:
Start date:
04/13/2026
Due date:
04/15/2026
% Done:

100%

Estimated time:
(Total: 0:55 h)
Spent time:
(Total: 0:30 h)
SOC2 Control Reference:
Risk Level:
Low
Evidence Attached:
No
Compliance Due Date:
Change Type:
Standard
Change Category:
Environment:
Production
Rollback Plan:

Switch back to previous Version: 3.18.3.

Testing Evidence:
No
Approved By:
Implementation Date:
Post-Implementation Review:
Successful
Reported By (Internal):
Reported By (External):

Description

h2. Change Request: Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.

| Requester | David Leedom |
| Change Type | Standard |
| Category | |
| Environment | Production |
| Risk Level | Low |
| Planned Date | |

h3. Rollback Plan
Switch back to previous Version: 3.18.3.

h3. Approval Chain (CC5.2, CC8.1)

  • Requested by: David Leedom
  • Approved by: 6

Subtasks 3 (0 open3 closed)

Change Request #62: Testing Validation - Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.CompletedDavid Leedom04/13/202604/15/2026

Actions
Change Request #63: Security Review - Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.CompletedDavid Leedom04/13/2026

Actions
Change Request #64: Post-Implementation Review - Deploy Release 3.19.0 to handle both Legacy and Private VPC environments.CompletedDavid Leedom04/13/202604/14/2026

Actions

DL Updated by David Leedom 2 months ago Actions #1

  • Subtask #62 added

DL Updated by David Leedom 2 months ago Actions #2

  • Subtask #63 added

DL Updated by David Leedom 2 months ago Actions #3

  • Subtask #64 added

DL Updated by David Leedom 2 months ago Actions #4

  • Status changed from New to In Progress

I've tested this update buy loading in the old Development server and switching the test subdomain to point to.

My testing methodology was focused on trying to force the url to http. I tried these iterations:

In all cases the system successfully converted to https and switch to the login.php page.

DL Updated by David Leedom 2 months ago Actions #5

  • Status changed from In Progress to Pending Approval
  • Testing Evidence set to No
  • Post-Implementation Review set to Successful

After deployment everything looks good.

Pull Request: Release 3.19.0 - AWS Private Security platform migration

DL Updated by David Leedom 2 months ago Actions #6

  • Status changed from Pending Approval to Approved

DL Updated by David Leedom 2 months ago Actions #7

  • Status changed from Approved to Implementing

DL Updated by David Leedom 2 months ago Actions #8

  • Status changed from Implementing to In Review

DL Updated by David Leedom 2 months ago Actions #9

  • Status changed from In Review to Completed
Actions

Also available in: PDF Atom