Kerberos错误：GSSHeader找不到正确的标记 [英] Kerberos error: GSSHeader did not find the right tag

问题描述

我正在尝试将Kerberos身份验证连接到SOAP服务wsdl url。
我能够成功建立连接并进行服务呼叫。
启动服务器后，我至少可以拨打一次成功的服务电话。
但是在几次请求（1次或更多次）之后，我突然收到无效的令牌错误。
一旦我收到错误，未来的呼叫就不起作用而且错误仍然存​​在。

I’m trying to make Kerberos authentication connection to a SOAP service wsdl url. I’m able to establish connection successfully and make service calls. After I start my server, I’m able to make successful service call at least once. However after few requests (1 or more ), I suddenly get invalid token error. Once I get the error, future calls do not work and error persists.

如果我重启服务器，那么服务呼叫至少会工作一次。上面的循环继续。

IF I restart my server, then again service call works at least once. And above cycle continues.

我无法弄清楚为什么突然令牌失效，尽管之前有效。 重启服务器使令牌再次有效。

I’m unable to figure out why suddenly token gets invalid, though it worked earlier. And restarting server makes token valid again.

这是错误堆栈跟踪：

Caused by: GSSException: Defective token detected (Mechanism level: GSSHeader did not find the right tag)
        at sun.security.jgss.GSSHeader.<init>(GSSHeader.java:97)
        at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:237)
        at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)

推荐答案

我找不到令牌无效的根本原因。但这是我如何解决这个问题。

I could not find root cause for why token is invalid. But here is how i get around this issue.

我的身份验证在我重新启动服务器后第一次工作，并且bean在上下文中再次加载。所以我将spring bean的范围更改为 prototype ，以便每次创建新的代理bean时。

My authentication was working for first time after I restart my server and bean is loaded again in context. So I changed scope of my spring bean to prototype so that every time new proxy bean is created.

这篇关于Kerberos错误：GSSHeader找不到正确的标记的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！