Page MenuHomePhabricator

[services] Allow browsers to access prod identity from comm.software
ClosedPublic

Authored by ashoat on Tue, Nov 5, 9:56 AM.
Tags
None
Referenced Files
F3168106: D13881.id45621.diff
Thu, Nov 7, 5:31 AM
F3168095: D13881.id45622.diff
Thu, Nov 7, 5:28 AM
F3168056: D13881.id45623.diff
Thu, Nov 7, 5:26 AM
F3168055: D13881.id.diff
Thu, Nov 7, 5:26 AM
F3167809: D13881.id45622.diff
Thu, Nov 7, 4:35 AM
F3167016: D13881.diff
Thu, Nov 7, 3:20 AM
F3166159: D13881.diff
Thu, Nov 7, 12:38 AM
F3166016: D13881.diff
Wed, Nov 6, 11:49 PM
Subscribers

Details

Summary

This diff updates the CORS config for the identity service in production to allow incoming connections from browsers rendering comm.software and www.comm.software.

Context for why we need this is in ENG-9862.

Test Plan

Terraform precommit hooks passed. Beyond that, not sure how to test this besides deploying to prod...

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Don't include port in web.comm.app

ashoat published this revision for review.Tue, Nov 5, 9:57 AM
ashoat edited the test plan for this revision. (Show Details)
varun accepted this revision.EditedTue, Nov 5, 9:59 AM

do you need the www origin?

This revision is now accepted and ready to land.Tue, Nov 5, 9:59 AM

For SLDs I've always included www.. Probably not as relevant anymore, but in the past it was something that some computers and some people would include when navigating to an SLD

This revision was landed with ongoing or failed builds.Tue, Nov 5, 10:02 AM
This revision was automatically updated to reflect the committed changes.

This was an unsafe change and is causing deployment failures in production. I think @varun was wrong in his assessment that the port could be skipped for web.comm.app.