That was one of the API changes introduced with the Network Service and as far as I know, you can't set the cookies storage path at runtime now.
This information is available in the CEF project :
Remove methods that modify cookie storage at runtime (see issue #2622).
This change removes cookie and request handler functionality that will not supported by the NetworkService. Specifically, it is no longer possible to change cookie storage locations at runime by returning a different CefCookieManager for an already initialized CefRequestContext. After this change you will need to use a separate CefRequestContext when creating a CefBrowser if you require separate cookie storage.
The following methods have been removed: - CefCookieManager::CreateManager - CefCookieManager::GetBlockingManager - CefCookieManager::SetStoragePath - CefRequestContextHandler::GetCookieManager
The following methods have been renamed: - CefRequestContext::GetDefaultCookieManager to GetCookieManager.
This change substantially simplifies the network implementation in CEF because it is no longer necessary to proxy objects that are normally owned by Chromium. Chromium patches that are no longer necessary will be removed as a follow-up commit.
To test: Verify that ceftests --gtest_filter=-PluginTest.* pass with NetworkService disabled. Plugin tests will be fixed in a follow-up commit.
https://bitbucket.org/chromiumembedded/ ... orkserviceAs suggested by Marshall in that comment, you can use a separate CefRequestContext for each user.