After updating all dependencies according to the demo, I get an IOException in the Waffle class NegotiateSecurityFilter on line 114:
com.sun.jna.platform.win32.Win32Exception: A token sent to the function is invalid.
No WindowsPrincipal is being created because of this. I read the issues about this and found these solutions, which seems to say the same thing:
"what fixed it for us was adding the SPN HTTP/[domain] and HTTPS/[domain] for the server service account."
"Issue got resolved by adding SPNs for that service account."
Is it now mandatory for Waffle to add a SPN for a server service account? I talked to our network technicians about adding a SPN, but they had never done that for a system before. They said that it would lead to several complications for the servers and the local development environment.
After updating all dependencies according to the demo, I get an IOException in the Waffle class NegotiateSecurityFilter on line 114:
com.sun.jna.platform.win32.Win32Exception: A token sent to the function is invalid.
No WindowsPrincipal is being created because of this. I read the issues about this and found these solutions, which seems to say the same thing:
"what fixed it for us was adding the SPN HTTP/[domain] and HTTPS/[domain] for the server service account." "Issue got resolved by adding SPNs for that service account."
Is it now mandatory for Waffle to add a SPN for a server service account? I talked to our network technicians about adding a SPN, but they had never done that for a system before. They said that it would lead to several complications for the servers and the local development environment.