[
https://issues.apache.org/jira/browse/FELIX-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved FELIX-3984.
------------------------------------
Resolution: Fixed
Added support with rev 1459204 along with testcase.
Unless overridden by settings of ConfigurationSpi the LoginModule would be
bound to application name 'other' if no explicit value is defined
> Use default application/realm name of 'other' if none specified
> ---------------------------------------------------------------
>
> Key: FELIX-3984
> URL: https://issues.apache.org/jira/browse/FELIX-3984
> Project: Felix
> Issue Type: Improvement
> Components: JAAS
> Affects Versions: jaas-1.0.0
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
>
> Any LoginModule registered via config or factory SHOULD provide a
> realm/application name. However if none is specified then the realm name
> should be assumed to be 'other'.
> Following should be supported
> 1. In case no realm name specified via 'jaas.realmName' the value should be
> set to 'other'
> 2. This default value can be changed by Admin via Configuration Spi settings
> and set it to any other value
> The significance of using 'other' here is that LoginContext would first check
> config entry for provided applicationName. If none is found then it looks for
> config entry for an app name 'other'. So for default setup LoginModules which
> does not have any appname specified would be considered as part of 'other'.
> if the admin changes that then no such default logic would be used
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
