[jira] [Resolved] (KARAF-1394) Custom login modules not seen with Equinox

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-1394.
-----------------------------------------

    Resolution: Fixed
    
> Custom login modules not seen with Equinox
> ------------------------------------------
>
>                 Key: KARAF-1394
>                 URL: https://issues.apache.org/jira/browse/KARAF-1394
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.2.6
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.8, 2.3.0, 3.0.0
>
>
> An user define a "custom" login module, for instance, in the blueprint descriptor of its own bundle:
>                   <jaas:config name="karaf " rank="1">
>                       <jaas:module className="org.apache.karaf.jaas.modules.jdbc.JDBCLoginModule" flags="required">
>                           datasource = osgi:javax.sql.DataSource/(osgi.jndi.service.name=jdbc/karafdb)
>                           query.password = SELECT PASSWORD FROM USERS WHERE USERNAME=?
>                           query.role = SELECT ROLE FROM ROLES WHERE USERNAME=?
>                       </jaas:module>
>                   </jaas:config>
> with a default Karaf instance (using Felix OSGi framework), the jaas:realms command shows the default PropertiesLoginModule and the user one.
> However, if the user switch to Equinox OSGi framework, only the default PropertiesLoginModule is seen, not the user one when performing jaas:realms.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira