引發的Java weblogic錯誤：java.lang.IllegalArgumentException

Question

當我嘗試使用sftp從源服務器向目標服務器推送一些批量上載時，我們面臨以下錯誤。

在weblogic上運行的此應用程序的后端。

Caused by: java.lang.IllegalArgumentException: No Configuration was registered that can handle the configuration named com.sun.security.jgss.krb5.initiate
    at com.bea.common.security.jdkutils.JAASConfiguration.getAppConfigurationEntry(JAASConfiguration.java:124)
    at sun.security.jgss.LoginConfigImpl.getAppConfigurationEntry(LoginConfigImpl.java:139)
    at javax.security.auth.login.LoginContext.init(LoginContext.java:243)
    at javax.security.auth.login.LoginContext.<init>(LoginContext.java:499)
    at sun.security.jgss.GSSUtil.login(GSSUtil.java:244)
    at sun.security.jgss.krb5.Krb5Util.getTicket(Krb5Util.java:136)
    at sun.security.jgss.krb5.Krb5InitCredential$1.run(Krb5InitCredential.java:328)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.security.jgss.krb5.Krb5InitCredential.getTgt(Krb5InitCredential.java:325)
    at sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:128)
    at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:106)
    at sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:172)
    at sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:209)
    at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:195)
    at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:162)
    at com.jcraft.jsch.jgss.GSSContextKrb5.init(GSSContextKrb5.java:129)
    at com.jcraft.jsch.UserAuthGSSAPIWithMIC.start(UserAuthGSSAPIWithMIC.java:135)
    at com.jcraft.jsch.Session.connect(Session.java:419)
    at com.jcraft.jsch.Session.connect(Session.java:150)
    at org.apache.commons.vfs.provider.sftp.SftpClientFactory.createConnection(SftpClientFactory.java:210)

Answer 1

你有JAAS配置文件嗎？ 如果你這樣做，那么你可能有舊的“啟動”部分格式 - com.sun.security.jgss.initiate，請注意它缺少“.krb5”。 它應該是com.sun.security.jgss.krb5.initiate。

或者，服務器啟動命令行中的配置文件路徑可能不正確。