Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ELY-762] Move SaslClientFactory handling to AuthenticationConfiguration #558

Merged
merged 5 commits into from Nov 17, 2016

Conversation

darranl
Copy link
Contributor

@darranl darranl commented Nov 17, 2016

No description provided.

@darranl
Copy link
Contributor Author

darranl commented Nov 17, 2016

The Remoting side of the changes are here jboss-remoting/jboss-remoting#84

private final Supplier<SaslClientFactory> saslClientFactorySupplier;

SetSaslClientFactoryAuthenticationConfiguration(final AuthenticationConfiguration parent, final Supplier<SaslClientFactory> saslClientFactorySupplier) {
super(parent.without(SetSaslClientFactoryAuthenticationConfiguration.class));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "without" here is redundant as the base class already ensures the same class doesn't exist on the chain.

@dmlloyd
Copy link
Contributor

dmlloyd commented Nov 17, 2016

Otherwise looks OK.

@dmlloyd
Copy link
Contributor

dmlloyd commented Nov 17, 2016

See http://lists.jboss.org/pipermail/wildfly-dev/2016-November/005545.html - it's generally not a good practice to have "bad" commits with subsequent "fix" commits, because it leaves wrong code in the upstream history, makes bisect less likely to work, etc.

@dmlloyd dmlloyd added the +1 DML label Nov 17, 2016
@fjuma fjuma added the +1 FJ label Nov 17, 2016
@fjuma fjuma merged commit e74d80f into wildfly-security:master Nov 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants