Re: Migrating to elytron

[Daniel Novo]

Hi Berke,

There is no equivalent to LdapLoginModule in Elytron, only LdapExtendedLoginModule -> LdapRealm.

Check this threads: 

https://groups.google.com/g/wildfly/c/8f5AAcoU7HY/m/traTruR_AQAJ

https://groups.google.com/g/wildfly/c/I0TIH1CKGII/m/ji6_kGLuAAAJ

On Wed, Dec 20, 2023 at 5:50 PM Berke Soysal <soysalb...@gmail.com> wrote:

Hi,
As we migrate from eap 7.3 to Wildly 26.1.1 migrating to elytron needed. As I'm not familiar I was following the steps in  WildFly Elytron Security

But the legacy security we use for authentication has not a match as far as I can see in our configuration.
Any help is much appreciated. Thanks.

<security-domain name="login" cache-type="default">
<authentication>
<login-module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required">
<module-option name="java.naming.provider.url" value="${java.naming.provider.url}"/>
<module-option name="principalDNPrefix" value="${principalDNPrefix}"/>
<module-option name="principalDNSuffix" value="${principalDNSuffix}"/>
<module-option name="com.sun.jndi.ldap.connect.timeout" value="${ldap.connect.timeout}"/>
</login-module>
</authentication>
</security-domain>

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/e6eaa4b1-a70e-4b7a-bf94-b287f361e56cn%40googlegroups.com.

--

--------------

Daniel Novo

[Berke Soysal]

Hi Daniel,

What does this mean? If i would create a ldap-realm and security-domain related, and dir-context, I would be fine? Or do I need changes elsewhere?

 

Because I kinda tried to change the configuration but I'm getting  No LoginModules configured for login

[Berke Soysal]

<security-domain name="rds-login" default-realm="rds-login" permission-mapper="default-permission-mapper">
<realm name="rds-login"/>
</security-domain>

<ldap-realm name="rds-login" dir-context="ldapDirContext" direct-verification="true">
<identity-mapping rdn-identifier="uid" search-base-dn="ou=people,dc=secret,dc=secret,dc=de"/>
</ldap-realm>

<dir-contexts>
<dir-context name="ldapDirContext" url="ldaps://secret" authentication-level="none"/>
</dir-contexts>

basically this are my settings. still The rds-login is not created.