When server starts there is no check whether some unexpected attribute is part of any of elements in PicketLink Subsystem (both, Federation and Identity Management). It can leads to critical issues when XML configuration is set manually. 

For example, customer can erroneously manually write "ssl-authnetication" instead of "ssl-authentication" which caused that attribute ssl-authentication is not set even though customer thinks it works correctly - no exception is thrown during server booting and server starts correctly.

Unexpected attribute should cause javax.xml.stream.XMLStreamException same as it is in another subsystems.