Browse Source

sasl-javax: Do not set system properties in SASLGSSAPIMechanism

Smack did this for a long time, since eb56f8a55 ("GSSAPI work by Jay
Kline (SMACK-218)."). Not always in a static block though. But
irregardless this is bad practice as it causes side-effects and may
overrides settings.

For example, one users reports:

java.lang.SecurityException: java.io.IOException: gss.conf (No such file or directory)
    at sun.security.provider.ConfigFile$Spi.<init>(ConfigFile.java:137)
    at sun.security.provider.ConfigFile.<init>(ConfigFile.java:102)
    at sun.reflect.GeneratedConstructorAccessor119.newInstance(Unknown Source)
clusterIntTest
Florian Schmaus 8 months ago
parent
commit
35cf094386
1 changed files with 0 additions and 5 deletions
  1. +0
    -5
      smack-sasl-javax/src/main/java/org/jivesoftware/smack/sasl/javax/SASLGSSAPIMechanism.java

+ 0
- 5
smack-sasl-javax/src/main/java/org/jivesoftware/smack/sasl/javax/SASLGSSAPIMechanism.java View File

@@ -29,11 +29,6 @@ public class SASLGSSAPIMechanism extends SASLJavaXMechanism {

public static final String NAME = GSSAPI;

static {
System.setProperty("javax.security.auth.useSubjectCredsOnly", "false");
System.setProperty("java.security.auth.login.config", "gss.conf");
}

@Override
public boolean authzidSupported() {
return true;


Loading…
Cancel
Save