geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-4379) Default to get from JVM's JAAS Configuration if it is not found in Geronimo's own implementation
Date Thu, 23 Feb 2012 09:03:48 GMT

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

Ivan resolved GERONIMO-4379.
----------------------------

    Resolution: Won't Fix

Seem that there is no scenario to require this function.
                
> Default to get from JVM's JAAS Configuration if  it is not found in Geronimo's own implementation
> -------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4379
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4379
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>         Environment: JDK 1.5/Windows XP
>            Reporter: Ivan
>            Priority: Minor
>             Fix For: Wish List
>
>         Attachments: Geronimo-4379.patch
>
>
> While configuring the JAAS Login in the Geronimo, I just found that we use GeronimoLoginConfiguration
to replace the JVM's ConfigurationFile, shall we give an opportunity to let the user to get
the config from JVM's Configuration.
> For example, first, we could  check from Gronimo's setting, if null is returned, we could
invoke oldConguration.getAppConfigurationEntry(name). 

--
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

        

Mime
View raw message