Hi all,
I try to use the Waffle-filter example in my GWT Application on a tomcat 9.
My workflow:
- Add the filter of the example to the web.xml
- Do a RPC-Call
- Get User Principal in the ServiceImpl RPC-method --> returns null
Code snippet in the method of the ServiceImpl:
HttpServletRequest request = getThreadLocalRequest();
request.getSession().getId(); //works ruturns the correct session
request.getRemoteUser(); //returns null
Principal principal = request.getUserPrincipal(); //returns null
Is the workflow correct or do I have to do anything more/diffrent?
In the network trace of the waffle-filter example there is a "WWW-Authenticate:
Negotiate oRswG..." in the Response Header and in the Request Header I find the "
Authorization:
Negotiate oXcwdaADCgEBolo...". In the GWT-App network trace of the RPC-Call I miss these Attributes, so there is no authentication made.
In the tomcat log I can see that while deploying the waffle filter is load ("INFO waffle.servlet.spi.SecurityFilterProviderCollection - loading 'waffle.servlet.spi.NegotiateSecurityFilterProvider'", not?). Deploying ends without errors.
Please help me to get that to work.
In addition to that I have to establish authentication to a windows domain controller which isn't in the same domain / active directory as the server and the domains don't trust each other. So I cannot use waffle, not? Can I combine a JCIFS-filter for the other domain and the waffle-filter for the authentication to the same domain?
Thanks for your help in advance.
Dennis