The only area where I was involved is calendar and the issues I had where cookie related. If two connections to the same server but different accounts where made (url.spec being identical), the server mixed them up and one failed because it was using the others auth cookie. The solution was to enforce a unique userContextId per principal. See bug 1544596. https://searchfox.org/comm-central/source/calendar/base/modules/utils/calProviderUtils.jsm#62 https://searchfox.org/comm-central/source/calendar/base/modules/utils/calProviderUtils.jsm#71 Does that help?
Bug 1699057 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The only area where I was involved is calendar and the issues I had where cookie related. If two connections to the same server but different accounts where made (url.spec being identical), one of them failed because it was using the others auth cookie. The solution was to enforce a unique userContextId per principal. See bug 1544596. https://searchfox.org/comm-central/source/calendar/base/modules/utils/calProviderUtils.jsm#62 https://searchfox.org/comm-central/source/calendar/base/modules/utils/calProviderUtils.jsm#71 Does that help?
The only area where I was involved is calendar and the issues I had where cookie related. If two connections to the same server but different accounts where made (url.spec being identical), one of them failed because it was using the others auth cookie. The solution was to enforce a unique userContextId per principal. See bug 1544596. https://searchfox.org/comm-central/rev/33fdb2afed98b1241830e418e9107e36d125e210/calendar/base/modules/utils/calProviderUtils.jsm#62 https://searchfox.org/comm-central/rev/33fdb2afed98b1241830e418e9107e36d125e210/calendar/base/modules/utils/calProviderUtils.jsm#71 Does that help?