Bug 1099055
| Summary: | Authentication configuration builder requires CallbackHandler also when subject it set | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Vojtech Juranek <vjuranek> |
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.0 | CC: | gsheldon, jdg-bugs |
| Target Milestone: | ER6 | ||
| Target Release: | 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The Hot Rod Java client configuration validator does not accept a configuration where the SASL callback handler is not set. However, if a valid client Subject is supplied instead, the validator accepts the configuration. As a result, the configuration validator throws a org.infinispan.commons.CacheConfigurationException exception with the following error message: ISPN004030: Cannot enable authentication without specifying a Callback Handler.
A workaround for this issue is to supply a callbackhandler with an empty handle() method as follows:
public static final class NoOpCallbackHandler implements CallbackHandler {
public static final NoOpCallbackHandler INSTANCE = new NoOpCallbackHandler();
@Override
public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {
// NO OP
}
}
As a result, the configuration validator accepts the configuration and SASL authentication works as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-26 14:04:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1104639 | ||
|
Description
Vojtech Juranek
2014-05-19 11:41:22 UTC
This was fixed. We don't need to mention it in release notes unless we want to mention issues that were in Beta release notes and fixed for GA. |