In my case I actually store our Couchbase configuration in a totally separate XML configuration file from the Web.config. The reason for this is because we have so much other ‘app’ configuration stuff in our Web.config file that it makes it too complicated to maintain separate copies for every site that is running on our code. So rather we keep the Web.config file common to all sites that run the app, and store the site specific stuff in a SiteConfig.xml file for the site.
So we have or own mechanism for reading the Couchbase configuration and it was not entirely clear how to use the library verbatim for session storage. But looking through the code you can easily toss in your own factory that implements the ICouchbaseClientFactory interface with the following session state section in the config file:
This sample just points to the default CouchbaseClientFactory but you can replace that class with your own to be able to configure the client with your own configuration instead of expecting to get it from a section in the web.config file.