Issue9

Moved the setting of forced auth and passive to constructor of the LoginHandler rather than per request. Updated unit tests
It doesn't fail at all - we still send the "mixed message" and let CAS sort it out. But we log the warning so that the SHIB admin can recognize that they are sending CAS a mixed message that may or may not be handled appropriately. This behavior is the same as it was before.