[JBoss JIRA] Created: (GTNPORTAL-255) Do not Configure aplication policy inside server/default/conf/login-config.xml
6:02 p.m.
Do not Configure aplication policy inside server/default/conf/login-config.xml
------------------------------------------------------------------------------
Key: GTNPORTAL-255
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-255
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta01
Reporter: Patrice Lamarque
For now, the jaas conf lives in server/default/conf/login-config.xml
<application-policy name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required"></login-module>
</authentication>
</application-policy>
It would be more portable to embed it inside gatein.ear such as explained here :
https://jira.jboss.org/jira/browse/JBAS-2063
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-255) Do not Configure aplication policy inside server/default/conf/login-config.xml
[
https://jira.jboss.org/jira/browse/GTNPORTAL-255?page=com.atlassian.jira....
]
Patrice Lamarque commented on GTNPORTAL-255:
--------------------------------------------
Or perhaps an xxx-jboss-beans.xml is more appropriate for AS5 :
http://server.dzone.com/articles/security-features-jboss-510
Do not Configure aplication policy inside
server/default/conf/login-config.xml
------------------------------------------------------------------------------
Key: GTNPORTAL-255
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-255
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta01
Reporter: Patrice Lamarque
For now, the jaas conf lives in server/default/conf/login-config.xml
<application-policy name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required"></login-module>
</authentication>
</application-policy>
It would be more portable to embed it inside gatein.ear such as explained here :
https://jira.jboss.org/jira/browse/JBAS-2063
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-255) Do not Configure aplication policy inside server/default/conf/login-config.xml
[
https://jira.jboss.org/jira/browse/GTNPORTAL-255?page=com.atlassian.jira....
]
Patrice Lamarque commented on GTNPORTAL-255:
--------------------------------------------
To be more specific, you just need to add a gatein.ear/META-INF/gatein-jboss-beans.xml and
stick this in it :
<deployment xmlns="urn:jboss:bean-deployer:2.0">
<application-policy xmlns="urn:jboss:security-beans:1.0"
name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required">
<module-option
name="portalContainerName">portal</module-option>
<module-option name="realmName">exo-domain</module-option>
</login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required">
<module-option
name="portalContainerName">portal</module-option>
<module-option name="realmName">exo-domain</module-option>
</login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required">
<module-option
name="portalContainerName">portal</module-option>
<module-option name="realmName">exo-domain</module-option>
</login-module>
</authentication>
</application-policy>
</deployment>
After that you no longer need to override login-config.xml in
exo.portal.server.jboss.patch
Do not Configure aplication policy inside
server/default/conf/login-config.xml
------------------------------------------------------------------------------
Key: GTNPORTAL-255
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-255
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta01
Reporter: Patrice Lamarque
For now, the jaas conf lives in server/default/conf/login-config.xml
<application-policy name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required"></login-module>
</authentication>
</application-policy>
It would be more portable to embed it inside gatein.ear such as explained here :
https://jira.jboss.org/jira/browse/JBAS-2063
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:34 p.m.
New subject: [JBoss JIRA] Assigned: (GTNPORTAL-255) Do not Configure aplication policy inside server/default/conf/login-config.xml
[
https://jira.jboss.org/jira/browse/GTNPORTAL-255?page=com.atlassian.jira....
]
Thomas Heute reassigned GTNPORTAL-255:
--------------------------------------
Assignee: Thomas Heute
Do not Configure aplication policy inside
server/default/conf/login-config.xml
------------------------------------------------------------------------------
Key: GTNPORTAL-255
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-255
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta01
Reporter: Patrice Lamarque
Assignee: Thomas Heute
For now, the jaas conf lives in server/default/conf/login-config.xml
<application-policy name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required"></login-module>
</authentication>
</application-policy>
It would be more portable to embed it inside gatein.ear such as explained here :
https://jira.jboss.org/jira/browse/JBAS-2063
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 p.m.
New subject: [JBoss JIRA] Resolved: (GTNPORTAL-255) Do not Configure aplication policy inside server/default/conf/login-config.xml
[
https://jira.jboss.org/jira/browse/GTNPORTAL-255?page=com.atlassian.jira....
]
Thomas Heute resolved GTNPORTAL-255.
------------------------------------
Resolution: Done
I've also added a MC descriptor in sample-portal.ear to define its application
security policy
Do not Configure aplication policy inside
server/default/conf/login-config.xml
------------------------------------------------------------------------------
Key: GTNPORTAL-255
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-255
Project: GateIn Portal
Issue Type: Task
Components: Packaging
Affects Versions: 3.0.0-Beta01
Reporter: Patrice Lamarque
Assignee: Thomas Heute
For now, the jaas conf lives in server/default/conf/login-config.xml
<application-policy name="exo-domain">
<authentication>
<login-module code="org.exoplatform.web.security.PortalLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.jaas.SharedStateLoginModule"
flag="required"></login-module>
<login-module
code="org.exoplatform.services.security.j2ee.JbossLoginModule"
flag="required"></login-module>
</authentication>
</application-policy>
It would be more portable to embed it inside gatein.ear such as explained here :
https://jira.jboss.org/jira/browse/JBAS-2063
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5338
days inactive
5340
days old
4 comments
2 participants
participants (2)
-
Patrice Lamarque (JIRA) -
Thomas Heute (JIRA)