Hi Runger, I can confirm that when I inizialized the Spnego filter in the class SpnegoFilterConfig it gets an AppConfigurationEntry in the method doClientModule and doServerModule with the following istruction :
AppConfigurationEntry appconfigurationentry = configuration.getAppConfigurationEntry(s)[0]; With this value in the LoginContext loaded by SPNEGO, Magnolia passes to the FormLogin filter but when it tries to performe the method authenticate in order to achive the Login Result I obtained the exception above.I think the problem is that SPNEGO loads its LoginContext (in this case the appConfigurateEntry are spnego-client and spnego-server but not magnolia) used by Magnolia instead the configuration written in the jaas.config file. In fact if I erase the Spnego filter from the list Magnolia finds out its LoginModule called "magnolia" registered in the file jaas.config. Do you know a workaround for this problem? Thank you in advance Regards from Milan Alberto -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=be26f4c1-1b80-42bc-8de0-c51be72a9127 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
