As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We would like to restrict folks with DEVELOPER security in Dev Studio to allow updating of only specific Domain files. We've found that anyone given developer access and the domain access can update the domains. We only want developers to be able to update thier personal domain, yet read other domains. Has anyone successfully done this? Any suggestions?
We are running 7.6 on Windows using Active Directory. Thanks in advance.
Since you are using AD anyway, why not tie in directory read/writes to the userid, where you give the user read access to the domain directories you want them to see, and read/write to the domains you want them to contribute to. I realize that this is a two step process, but it should at least achieve the desired result.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
Ya ... sorry about that I guess I didn't think that one all the way through.
Application files (/ibi/apps directory) are under the control of the reporting server, and as such, can take advantage of OS level directory rights - such as AD if you are running under windows. The problem here is that MRE is actually controlled and written to by the web application (ibi_apps). When content is created in MRE, it is created solely by the web app without any involvement from the reporting server. Therefore - I think - that OS level security is bound to the credentials of the web app or application server.
If this is true, then I suspect that authorization for disk writes is handled programmatically by the web app. In other words, you would probably have to request some security changes to the existing MRE roles to achieve what you are looking for.
The key phrase above is "I think", so don't take my word for it!
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott