Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring boot 3 demo fails #1913

Open
hazendaz opened this issue Mar 26, 2023 · 3 comments
Open

Spring boot 3 demo fails #1913

hazendaz opened this issue Mar 26, 2023 · 3 comments
Assignees

Comments

@hazendaz
Copy link
Member

No description provided.

@nclemeur
Copy link

nclemeur commented Dec 9, 2024

Not much description about this issue, but I am wondering if it would be similar to the one I am encountering. I have the following in the logs...

[http-nio-8889-exec-6] INFO w.spring.NegotiateSecurityFilter.doFilter - successfully logged in user: DOMAIN\user [http-nio-8889-exec-6] WARN w.spring.NegotiateSecurityFilter.doFilter - error logging in user: com.sun.jna.platform.win32.Win32Exception: The logon attempt failed [http-nio-8889-exec-7] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet].log - Servlet.service() for servlet [dispatcherServlet] threw exception java.lang.RuntimeException: Invalid Authorization header: Negotiate at waffle.util.AuthorizationHeader.getSecurityPackage(AuthorizationHeader.java:96)

Strangely the ERROR message seems to be a different thread than the info and warning messages...

Any idea on how to progress from here... Very similar code was working fine with spring boot 2.x

Any idea

@hazendaz
Copy link
Member Author

Sorry I should have written more here. I forgot all about this. If you take the project and build it then go into the demo folder and find the spring boot 3 module, try to execute it from there it had some issue. I don't recall the exact issue and believe it works otherwise. I think there was as ticket in last month or two where someone worked out issues with spring boot 3. I don't have time right now to look at this but may towards end of the month.

@nclemeur
Copy link

Thanks for the answer. That gave me the confidence to push a bit further in my investigation, and I now have a working solution with a very simplified version of my old code. So I am confident I'll get it working with all the features I need very soon.

When searching, I came across issue #1472 and I thought this was still an unresolved problem. I still don't know what was the breaking part, but if I found it I will report here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants