Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-13470

Ldap UserPasswordCredentialLoaderBuilder shouldn't be added by default

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 14.0.0.Final
    • 13.0.2.Final, 14.0.0.Final
    • Integration
    • None

      As a developer, I would like to connect to RHDS.

      During my investigation, I found that while connecting to RHDS, we shouldn't add UserPasswordCredentialLoaderBuilder

      In this case, instead of creating a bool property, I decided to set LdapUserPasswordMapperConfiguration.FROM as null by default. When it has a value, then there is an opportunity to set also the VERIFIABLE attribute value. Adding the UserPasswordCredentialLoader and when VERIFIABLE is true are different things.

      org.wildfly.security.auth.realm.ldap.LdapSecurityRealmBuilder

              public LdapSecurityRealmBuilder build() {
                  assertNotBuilt();
                  built = true;
      
                  UserPasswordCredentialLoader upcl = new UserPasswordCredentialLoader(userPasswordAttribute);
                  LdapSecurityRealmBuilder.this.addCredentialLoader(upcl);
                  if (enablePersistence) LdapSecurityRealmBuilder.this.addCredentialPersister(upcl);
                  if (enableVerification) LdapSecurityRealmBuilder.this.addEvidenceVerifier(upcl.toEvidenceVerifier());
      

              dlovison@redhat.com Diego Lovison
              dlovison@redhat.com Diego Lovison
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: