10:57 a.m.
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role hardcoded somewhere
[ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_1237... ]
Luc Boudreau commented on JBPORTAL-1733:
----------------------------------------
On the last thing to do, I meant :
- - Try to secure the root node : Access Denided
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:01 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-1733) CMS admin role hardcoded somewhere
[ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=all ]
Thomas Heute updated JBPORTAL-1733:
-----------------------------------
Fix Version/s: 2.6.3 Final
Affects Version/s: 2.6.2 Final
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
Fix For: 2.6.3 Final
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:45 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role hardcoded somewhere
[ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_1238... ]
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------
I just created JBPORTAL-1740. Sorry, didn't see this one.
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
Fix For: 2.6.3 Final
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:11 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-1733) CMS admin role hardcoded somewhere
[ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=comments#action_1238... ]
Tobias Roth commented on JBPORTAL-1733:
---------------------------------------
This is not the same as 1647. This issue is the same as 1740.
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
Fix For: 2.6.3 Final
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Resolved: (JBPORTAL-1733) CMS admin role hardcoded somewhere
[ http://jira.jboss.com/jira/browse/JBPORTAL-1733?page=all ]
Sohil Shah resolved JBPORTAL-1733.
----------------------------------
Resolution: Done
The following two aspects of CMS security and now made configurable:
1/ Ability to configure the CMS super user instead of the built-in admin user. This can be
achieved by the configuration inside the portal-cms.sar/META-INF/jboss-service.xml.
<mbean
code="org.jboss.portal.cms.security.AuthorizationProviderImpl"
name="portal:service=AuthorizationProvider,type=cms"
xmbean-dd=""
xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
<xmbean/>
<!--
NOTE: cmsRootUserName denotes a single Portal user that has access to everything in
the CMS. Denote this user
carefully and should be synonymous to the 'root' user in a Unix system. By
default: this value is the built-in
'admin' user account. This can be changed to any other user account
registered in your Portal
-->
<attribute name="CmsRootUserName">admin</attribute>
<depends optional-attribute-name="IdentityServiceController"
proxy-type="attribute">portal:service=Module,type=IdentityServiceController</depends>
</mbean>
2/ The Portal Role that has access to the CMS Security Console for setting up the
permissions on the CMS nodes can now be specified in the following file:
jboss-portal.sar/conf/identity/standardidentity-config.xml
<!--Common options section-->
<option-group>
<group-name>common</group-name>
<option>
<name>userCtxDN</name>
<value>ou=People,dc=example,dc=com</value>
</option>
<option>
<name>uidAttributeID</name>
<value>uid</value>
</option>
<option>
<name>passwordAttributeID</name>
<value>userPassword</value>
</option>
<option>
<name>roleCtxDN</name>
<value>ou=Roles,dc=example,dc=com</value>
</option>
<option>
<name>ridAttributeId</name>
<value>cn</value>
</option>
<option>
<name>roleDisplayNameAttributeID</name>
<value>cn</value>
</option>
<option>
<name>membershipAttributeID</name>
<value>member</value>
</option>
<option>
<name>membershipAttributeIsDN</name>
<value>true</value>
</option>
<!-- NOTE: defaultAdminRole is a required option -->
<option>
<name>defaultAdminRole</name>
<value>Admin</value>
</option>
</option-group>
CMS admin role hardcoded somewhere
----------------------------------
Key: JBPORTAL-1733
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1733
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.2 Final
Environment: Any
Reporter: Luc Boudreau
Assigned To: Sohil Shah
Fix For: 2.6.3 Final
- Modify platform to use another admin role name
- Create user with new admin role and old Admin role
- Change security on root node of CMS and make the new role the manager
- Change the user's roles by removing the old Admin role
- Try to manage the root node : Access Denided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6254
days inactive
6310
days old
5 comments
4 participants
participants (4)
-
Luc Boudreau (JIRA) -
Sohil Shah (JIRA)
-
Thomas Heute (JIRA)
-
Tobias Roth (JIRA)