Portal Server 7 - Functionality Queries!
To whom it may concern,
I need some documentation for the following things:
1. How to establish permissions for file sharing porlet. By default, all community members can read/write permission for file sharing porlet. I want to give certain community members only "READ" while others "READ/WRITE/DELETE" permissions.
2. When multiple domains/organizations are created by commadmin domain create utility, cross-domain communities are searchable/joinable by default. I want to restrict this functionality. For example abc.com users can only search/join abc.com organziation communities whereas xyz.com users can only search/join xyz.com communities. Because of the fact that all organizations share the same embedded Apache Derby database therefore by default cross-domain users can search/join cross-domains communities. I want to restrict this functionality.
Regards,
Farhan Ahmed.
Collaboration Team Lead,
InterActive Convergence, Pakistan.
# 1
hi,
for #1, you can not modify the default access control per action. each service defines what actions community visitors, members, and owners can perform, and this is not customizable.
this is a known problem that we hope to fix in the near future.
for #2, you want to create two different portals. community data is partitioned per portal, not per domain.
so in that case, you'd create an abc.com portal, and a xyz.com portal to mirror your abc,com and xyz.com orgs. in the abc.com org, you'd register the abc.com portal services, and in the xyz.com org you'd register the xyz.com portal services. the result is that if say a user in the abc.com ORG tries to log in to the xyz.com PORTAL, the portal will deny access, because the services for xyz.com PORTAL are not registered in the abc.com ORG.
i know this makes it sounds needlessly complex for your use case, but the system needs to support the converse scenario as well. e.g., orgs sharing community data, and users from different orgs accessing the same portal.
