Major Description
There are times when certain cookies need to not be allowed to be set. For instance, when using a Knox application to facilitate a central login page, the inclusion of the JSESSIONID cookie when interacting with the KnoxSSO service with the Shiro provider interferes with forcing the user to relogin.
This change will allow a topology to be crafted such that the login does not result in a JSESSIONID being set.