Testing has shown that attempting to share a single SOAuthorization object amongst several active sessions can lead to deadlocks during AppSSO authentication. Since the SOAuthorization object is meant to be stateless, there is no harm in constructing and destroying it for each type of authentication flow. This simplifies the logic, and makes it clear which SOAuthorization object is associated with a given load event.
<rdar://98413693>
Pull request: https://github.com/Webkit/WebKit/pull/3684
Committed 253929@main (bc90c50c6ba8): <https://commits.webkit.org/253929@main> Reviewed commits have been landed. Closing PR #3684 and removing active labels.