[
https://issues.apache.org/jira/browse/GERONIMO-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy closed GERONIMO-3654.
-----------------------------------------
Resolution: Fixed
Completed: At revision: 602089
o Copied o.a.g.s.jaas.NamedUPCredentailLoginModule to
o.a.g.s.realm.providers.NamedUsernamePasswordCredentialLoginModule
o Marked NamedUPCredentialLoginModule as deprecated
o Changed all references from o.a.g.s.jaas.NamedUPCredentialLoginModule to
o.a.g.s.realm.providers.NamedUsernamePasswordCredentialLoginModule
> Moving o.a.g.s.jaas.NamedUPCredentailLoginModule to o.a.g.s.realm.providers
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-3654
> URL: https://issues.apache.org/jira/browse/GERONIMO-3654
> Project: Geronimo
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: security
> Affects Versions: 2.0.x, 2.1
> Reporter: Vamsavardhana Reddy
> Assignee: Vamsavardhana Reddy
> Fix For: 2.0.x, 2.1
>
>
> David Jencks suggested that we move
> org.apache.geronmio.security.jaas.NamedUPCredentailLoginModule to
> org.apache.geronimo.security.realm.providers package. I intend to do the
> following.
> 1. svn copy org.apache.geronmio.security.jaas.NamedUPCredentailLoginModule to
> org.apache.geronimo.security.realm.providers.NamedUPCredentailLoginModule
> 2. Make org.apache.geronmio.security.jaas.NamedUPCredentailLoginModule extend
> org.apache.geronimo.security.realm.providers.NamedUPCredentailLoginModule.
> 3. Mark org.apache.geronmio.security.jaas.NamedUPCredentailLoginModule as
> deprecated.
> 4. Change all references from
> org.apache.geronmio.security.jaas.NamedUPCredentailLoginModule to
> org.apache.geronimo.security.realm.providers.NamedUPCredentailLoginModule
> Does anyone see this coming in the way of compatibility? I do not intend to
> change the option name
> "org.apache.geronimo.jaas.NamedUPCredentialLoginModule.Name" as this will
> surely break compatibility. Whether or not the move breaks compatibility,
> should we consider this move only in trunk and not in branches\2.0?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
