Hi Alberto, I'm sort of guessing here based on your error description.
But it sounds like magnolia can't find the JAAS configuration for the filter chain "magnolia", which normally gets initialized by magnolia on startup, based on the contents of the "jaas.config" file in WEB-INF/config Looking at the code at http://spnego.sourceforge.net/api/src-html/net/sourceforge/spnego/SpnegoFilterConfig.html (line 176, 178) the SPNegoFilterConfiguration is using JAAS. I assume you configure a reference to the "login.conf" file somewhere? --> this is the same type of file as the jaas.config file used by magnolia. (See: http://spnego.sourceforge.net/pre_flight.html Section "Test connection to KDC using HelloKDC.java", part 2) ) I think the secret to solving your problem will be to combine both these JAAS config files into one single file, and make sure that this file gets loaded. This should work fine, since you can define multiple different modules in the same JAAS config file. Regards from Vienna, Richard > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:user-list-owner@magnolia- > cms.com] Im Auftrag von Alberto Giovannone (via Magnolia Forums) > Gesendet: Donnerstag, 08. Mai 2014 14:45 > An: Magnolia User List > Betreff: [magnolia-user] Re: Problem with Windows Integrated > Authentication and Magnolia Authentication > > 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]> > ---------------------------------------------------------------- ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
