CAS-1410: Failure to create pgtIOU/PGT should not result in successful validation.

If either of the pgtIOU or PGT fail to be created, CAS validation response should not proceed as if validation was successful. Current case is that pgtIOU may be absent in the validation payload, as the proxy callback may timeout due to load, etc.
CAS-1410: Updated protocol to specify new proxy failure behavior
CAS-1410: Updated protocol to specify new proxy failure behavior
Fix for CAS-1412
CAS-1410: Addressed feedback. Updated formatting.
CAS-1412: web session terminated at end of subflow
Added code to check flowsession for root before setting maxInactiveInterval.
CAS-1412: web session terminated at end of subflow
Added code to check flowsession for root before setting maxInactiveInterval.
Removed duplicate license text from index.jsp
Merge branch 'master' into CAS-1410

Conflicts:
	cas-server-protocol/3.0/cas_protocol_3_0.html
	cas-server-protocol/3.0/cas_protocol_3_0.pdf
CAS-1410: Regenerated html/pdf templates
Merge pull request #385 from Unicon/master

Removed duplicate license text from index.jsp
Merge pull request #384 from lucastheisen/CAS-1412

CAS-1412:  web session terminated at end of subflow
Merge pull request #383 from Unicon/CAS-1410

CAS-1410: Failure to create pgtIOU/PGT should not result in successful validation
CAS-1411: Update protocol spec with details on proxy callback behavior

The commit updates the protocol to provide more implementation detail as for the conditions that need to be passed and verified for a successful proxy authentication scenario. Emphasis is on failure scenarios. Furthermore, changed the recommendation on the format of attributes that are extended in Appendix A to match the default behvior.
Merge pull request #387 from Unicon/CAS-1411

CAS-1411: Update protocol spec with details on proxy callback behavior
Fixing an LDAP connection leak
Homogenization of the usage of internal LdapUtils
Indentation fix
Merge pull request #394 from iorga-group/master

Fixing an LDAP connection leak + using internal LdapUtils
Fixing another potential LDAP connection leak