You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2006/11/13 13:04:38 UTC
[jira] Created: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
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
Reporter: Vamsavardhana Reddy
Fix For: 1.2
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
[jira] Updated: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=all ]
Vamsavardhana Reddy updated GERONIMO-2560:
------------------------------------------
Fix Version/s: 2.0
Affects Version/s: 2.0
Priority: Critical (was: Major)
> 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
> 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
[jira] Closed: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=all ]
Vamsavardhana Reddy closed GERONIMO-2560.
-----------------------------------------
Verified that the realm is usable in a web app.
> 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
[jira] Commented: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=comments#action_12457975 ]
David Jencks commented on GERONIMO-2560:
----------------------------------------
I learned a bit more xml today about xsi:type and substitution groups, some from http://davidbau.com/archives/2003/12/18/the_design_of_xmlbeans_part_3.html
basically the XmlObject.add(XmlObject) methods only deal with inheritance in the schema, not substitution groups. This explains why the gbean is being added with the element name "service" rather than "gbean". The result is a valid document. We either need to support xsi:type more or find a way to get the gbean element name in here.
> 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
[jira] Resolved: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ 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
[jira] Assigned: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "Dain Sundstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=all ]
Dain Sundstrom reassigned GERONIMO-2560:
----------------------------------------
Assignee: Vamsavardhana Reddy
> 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
[jira] Commented: (GERONIMO-2560) Realm added using SecurityRealm
portlet does not work
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2560?page=comments#action_12456564 ]
Vamsavardhana Reddy commented on GERONIMO-2560:
-----------------------------------------------
SecurityRealm portlet is currently generating a plan given below. There are no deployment errors.
But then the new realm does not get listed in the portlet and the realm could not be used for authentication.
What is wrong with this plan?
{code}
<module xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2">
<environment>
<moduleId>
<groupId>console.realm</groupId>
<artifactId>myrealm</artifactId>
<version>1.0</version>
<type>car</type>
</moduleId>
<dependencies>
<dependency>
<groupId>org.apache.geronimo.configs</groupId>
<artifactId>j2ee-security</artifactId>
<type>car</type>
</dependency>
</dependencies>
</environment>
<service name="myrealm" class="org.apache.geronimo.security.realm.GenericSecurityRealm"
xsi:type="dep:gbeanType" xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<attribute name="realmName">myrealm</attribute>
<reference name="ServerInfo">
<name>ServerInfo</name>
</reference>
<reference name="LoginService">
<name>JaasLoginService</name>
</reference>
<xml-reference name="LoginModuleConfiguration">
<log:login-config xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-1.2">
<log:login-module control-flag="REQUIRED" server-side="true" wrap-principals="false">
<log:login-domain-name>myrealm</log:login-domain-name>
<log:login-module-class>
org.apache.geronimo.security.realm.providers.PropertiesFileLoginModule
</log:login-module-class>
<log:option name="usersURI">var/security/users.properties</log:option>
<log:option name="groupsURI">var/security/groups.properties</log:option>
</log:login-module>
</log:login-config>
</xml-reference>
</service>
</module>
{code}
> 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
> 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