You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2006/12/13 03:08:21 UTC
[jira] Resolved: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=all ]
David Jencks resolved GERONIMO-2560.
------------------------------------
Resolution: Fixed
I think I fixed this trunk rev 486453, 1.2 rev. 486454 by setting the qname using an XmlCursor. The realm shows up in the realm portlet and seems to deploy ok. I didn't try to use it in an app.
I'd appreciate someone testing this a bit more and closing the issue.
> Realm added using SecurityRealm portlet does not work
> -----------------------------------------------------
>
> Key: GERONIMO-2560
> URL: http://issues.apache.org/jira/browse/GERONIMO-2560
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, security
> Affects Versions: 1.2, 2.0
> Reporter: Vamsavardhana Reddy
> Assigned To: Vamsavardhana Reddy
> Priority: Critical
> Fix For: 1.2, 2.0
>
>
> A new security realm added using SecurityRealm portlet does not get listed in the portlet. There are no deployment errors. Also, if an application is configured to authenticate against this realm, login is failing since the realm could not be found.
> The deployment plan for security realms generated in the console seems to use a "service" tag in place of "gbean" tag. If the service tag is changed to gbean tag, the realm is getting listed in the SecurityRealm portlet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira