Removing SWT authentication handler #10654
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Earlier in the year, I had already deactivated the SWT authentication handler (in this PR). Those changes have been fully released.
In this PR I'm just cleaning this dead code up now - removing the auth handler and supporting code. This handles incoming SWTs (no longer supported). I'll handle outbound SWTs in an upcoming PR. There are only 2 outbound calls SWTs are included on, and those can be controlled via hosting config. So for that, we'll do hosting config testing first, then follow up with code removal.
I will be backporting this to the in-proc branch, but no further.
Pull request checklist
IMPORTANT: Currently, changes must be backported to the
in-proc
branch to be included in Core Tools and non-Flex deployments.in-proc
branch is not requiredrelease_notes.md