[
https://issues.jboss.org/browse/SASL-49?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on SASL-49:
---------------------------------
As an alternative you could use {{Security.getProviders()}} with an appropriate filter and
filter the list that way, which wouldn't require any nonstandard behavior at all.
Custom Property to Prefer JDK Mechanisms
----------------------------------------
Key: SASL-49
URL:
https://issues.jboss.org/browse/SASL-49
Project: JBoss SASL Provider
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 2.0.0.Alpha1
This is primarily for testing although it could be used for other purposes, a new custom
property should be added to JBoss SASL which will cause mechanisms that duplicate JDK
supplied mechanisms to avoid being used themselves.
i.e. Even though JBoss SASL could supply an implementation for that mechanisms it will
let the JDK supplied version win through.
For testing this will enable interoperability testing between our mechanisms and the JDK
mechanisms, for end users they could use JBoss SASL for the new mechanisms we supply
whilst still using the JDK for the mechanisms it supplied.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)