This page includes a procedure to downgrade the user data from the 2.6 model to the 2.4 model. In a sharded system, however, the mongos won't detect that that the authorization model version has changed until its user cache is refreshed, which happens periodically according to the user cache invalidation interval or via manually running the invalidateUserCache command. We need to include something about this at the end of the downgrade docs.