[
https://issues.apache.org/jira/browse/JSEC-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671195#action_12671195
]
Les Hazlewood commented on JSEC-30:
-----------------------------------
Per the jsecurity-user mailing list, to help with context when fixing this
issue:
Csaba Nemeth wrote:
As I was testing the cause can be in the IniConfiguration class.
method createSecurityManagerForSection - line 184
It creates the default securityManager instance and puts into default under
'securityManager' and 'sm'.
As the configuration is read - I have only 'securityManager' defined. So
only that map entry is updated.
The 'sm' stays the default.
In the iterator where it pulls the realm factories it first pulls
'securityManager' - the overridden one - then 'sm' - so we are back to the
default settings.
If I change my ini - to have 'sm' insteadof 'securityManager' - all is fine.
But probably that is not what was intended.
Perhaps 'sm' should be put into the map after the iteration?
Jira?
> Aliases in the ini configuration builder do not work correctly
> --------------------------------------------------------------
>
> Key: JSEC-30
> URL: https://issues.apache.org/jira/browse/JSEC-30
> Project: JSecurity
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 0.9
> Reporter: Alan Cabrera
> Assignee: Alan Cabrera
> Fix For: 1.0
>
>
> Aliases in the ini configuration builder do not work correctly. When one
> gets updated the aliases do not. This can cause problems if one is
> explicitly creating a security manager and it gets overwritten by the default
> created and added w/ the "alias" sm. In this case the default replaces the
> explicitly created security manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
