[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-283: -------------------------------- Problem above was resolved, but currently there is JDK bug which looks currently prevents to use native GSS: In a lot of places in JDK there is *SunNativeProvider.INSTANCE* used, but it is initialized incorrectly - before list of supported GSS mechs is generated, so using this instance will raise exception - not existing mechanism: {code} GSSException: Provider SunNativeGSS does not support mechanism 1.2.840.113554.1.2.2 at java.security.jgss/sun.security.jgss.ProviderList.getMechFactory(ProviderList.java:253) at java.security.jgss/sun.security.jgss.ProviderList.getMechFactory(ProviderList.java:209) at java.security.jgss/sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:234) at java.security.jgss/sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:337) at java.security.jgss/sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:302) {code} It would be sufficient to change order of SunNativeProvider initializers, but it needs JDK patch. Reported to security-dev(a)openjdk.java.net list and will try to find workaround without JDK modification... -- This message was sent by Atlassian JIRA (v7.5.0#75005)