Problem restricting access to additional document directory

Hi,
Plattform: Win2K + iPlanet 6sp6
I'm having a bit of a problem setting restrictions on an addtional document directory (the "manual" directory is a good example).
I have a couple of virtual servers.
I do not want to use .htaccess.
Is it at all possible ?
any pointers ?
Best wishes,
B.L

Is it possible?Yes.
Any pointers?Umm. Use the "Restrict Access" screen to select the directory you want to restrict, and then set the permissions for it.
Without knowing what kind sof problems you're having we can't really make any recommendations.
Are you following the instructions in the Admin Guide?

Similar Messages

Setting Additional Document Directory in Sunone 6.1 SP1

Tried to run a testfile (index.htm) from an additional document directory in 6.1 SP1 on W2K (local), but it doesn't show up. What am I missing, doing wrong or forget?
Additional Document DIrectory setting:
Prefix: /test
Directory: c:/websites/test
in vsclass2.obj.conf (made a 2nd virtual class which is working for several sites) is written:
NameTrans fn="pfx2dir" from="/test" dir="c:/websites/test"
But I get this by using : http://hostname/test
Not Found
The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it.
Has it something to do with an ACL setting? If so, how do I control or config this?
Thanks for any assistance,
Ren�

Hi Dustin,
I think you posted this to the wrong newsgroup :-)
In WLS 6.1, document roots are Web Application specific. Unless you explicitly
change it, the default Web Application (the one that you get when you type in
the http://localhost:7001 URL), the document root is a folder under your domain's
application directory named "DefaultWebApp_{name-of-your-server}". Where {name-of-your-server}
is whatever value you assigned to the -Dweblogic.Name property, on the command
line you started WLS with. Refer to the WLS 6.1 documentation for instructions
on how to change this to a different Web Application. Here are a couple of links
that will provide you with some insight into this:
http://edocs.bea.com/wls/docs61/webapp/basics.html#136976
http://edocs.bea.com/wls/docs61/adminguide/web_server.html#113228
Regards,
Mike Wooten
"Dustin N. Jenkins" <[email protected]> wrote:
I have recently migrated from WebLogic 5.1 to WebLogic 6.1, on Windows
2000
running jdk 1.3.1. My Document Root settings (weblogic.httpd.documentRoot)
from WebLogic 5.1 in my weblogic.properties file did not carry over to
WebLogic 6.1, so does anybody know how to set the Document Root in WebLogic
6.1? Or is there an equivalent to it now?
Thanks in advance,
Dustin N. Jenkins

Restrict access to bw_metadata documents in WAD NW04S

Dear All,
We are deploying a new reporting and analysis application on NW04S BI.
In this application we set in a toolbar an access to some help documentation that are stored in KM as bw_metadata documents for the concerned web template (command OPEN_DIALOG_DLG_DOC_BROWSER).
But the problem is that every one is able to create, change and delete these documents !
I would like to restrict the access to these documents only in read for everyone and change for some power users.
In the permissions in KM, i cannot change access on this repository.
Did someone have an idea on how to change these permissions/authorizions ?
Thanks in advance for your suggestions.
Fred.

Fred,
sorry about that did not see the KM part...
help.sap.com still talks about setting up the BI document repository on the portal and not about KM when I did a search for OPEN_DIALOG_DLG_DOC_BROWSER ,
http://help.sap.com/saphelp_nw04s/helpdata/en/43/17348cfa923614e10000000a422035/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0901c9bb-0601-0010-49ab-c1770c527673
The WEB API does not seem to make a distinction betweek KM and the BDS . and not much given on single document..... maybe the single document is worth a try....
Arun
Hope it helps...
P.S BTW is the WEB API for 7.0 documented anywhere ? not able to find the same .. keep running into the 3.x version ....

Restricted access to confidential documents in DMS

Hello Gurus,
Need your expert guidance on the following requirement.
The requirement is to restrict the access of the document to users like Author, Reviewer and Approver, for all the documents.
I am confused which authorization object will work in my case and what settings I've to maintain for this.
Authorization Object C_DRAW_BGR u2014 Authorization Group
Authorization Object C_DRAW_DOK u2014 Document Access
Authorization Object C_DRAW_TCD u2014 Activities for Documents
Say I am having document types to us those are confidential.
ABC (finance docs)
LMN (Legal docs)
XYZ (design docs)
We want to allow only the users who are having below roles.
DMS_APPROVER
DMS_REVIEWER
For rest of the user we don't want to allow change/display acccess to the above documents.
Please guide me how to proceed, what need to be done.
Regards,
Ganesh

Hello Ravindra/DMS Gurus,
Sorry, but still my requirement is not met.
Actually our business scenario is as below:
Say there is a special document Type APR (Employee appraisal document)
And for 5 different employee created (Authors) the document giving their self-inputs.
Now these employee are assigned to say 3 different Supervisors (Reviewers) and one Manager (Approver)
{Author; Reviewer and Approver are maintained in Additional Data of the document.}
So each document will have a Reviewer and Approver assigned along with the Author.
Our requirement is to restrict the access of these 5 documents to the Employees (Authors), so that none of these employee can view each others document. And allow display/change to respective Supervisor (Reviewer) and Manager (Approver) only.
We need to restrict document access based on the above scenario
After checking, I think using authorization object the above requiremment can not be met. Can we use any user exit?
Your valuable comments are appreciated.
Regards,
Ganesh
Edited by: ganesh sarasvati on Aug 12, 2010 5:35 PM
Edited by: ganesh sarasvati on Aug 12, 2010 5:37 PM

Sharepoint 2010 restrict access to a document library unless loggin to domain

Have a requirement that has stumped me for awhile. we have a Sharepoint 2010 site that has some document libraries that have to be setup to ONLY allow users that are loggin to the domain to be able to access those libraries.
We are currently using active directory to authenicate user on login. and use active directory security groups for site, page and library access.
Any ideas if this is possible and if so where to start?

the easy answer: nothing built in can do that.
options can include: custom dev (potentially lots of it), "intelligent" app firewalls/proxies... but the practical answer is to either trust users with information, or disable public access (thus SP would *only* be accessible via LAN / VPN routing)
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

CHARM - Restrict access to other documents

Dear All,
When Change manager approves the CR & assign the developer, mail will trigger to developer & he will starts development, thats ok. If the ticket is not assigned to me and if i tried to open the UC, system should not allow me to open that ticket itself. How can we do this ? If my BP number is not assigned in that ticket, system should not allow me to open the ticket, is this possible ?
regds,
CB

Hello Kallumama
you have two different options to achieve this:
- first one is playing in CRMBS02 with the authorization codes. As a result, people will have access to tickets according to user status of ticket and not according to who the ticket is assigned to
- second one (and maybe better for you) is BAdI crm_order_auth_check. Thanks to MF 'CRM_ORDER_READ' you retrieve who is assigned to your ticket, then thank to a specific MF or to a Z evaluation path you ll have to get the BP assigned to SAP User who is trying to access to ticket; after comparaison if first is different from second then write an error message. That will not authorize User access in change mode to ticket !
Regards,
Khalil

Best way to restrict access to documents (outside of the group or library level)

Hi, we're thinking of implementing SharePoint Server 2013 Standard Edition for our organization. Many of our employees are research scientists working on proprietary information. From the (admittedly little) I understand about SharePoint, if a user wants
to restrict access to a particular document to the 2 or 3 people with whom they're collaborating (and also have it not appear in the search results), they will have to email their power user to request that a new document library be created in which they can
store their documents. Is that correct? In this case, what is the best way to handle item-level permissions? Users absolutely want to have the freedom to restrict access to their documents themselves rather than being forced to go to their power user. Thanks.

Hi,
Per my knowledge, if you want to restrict access to the documents to some users, then you need to have Manage Permissions permission to modify other users’ permission on the documents.
If you do not have the Manage Permissions permission, I recommend to ask the site administrator to create a workflow as below to remove the corresponding users’ permission on the documents which you uploaded. You can start the workflow on the document you
upload and then the permission of the users set on the workflow will be removed from the document.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

IWS60SP4 Additional Document Directories Problem with Web Application

We have iPlanet/Sunone WebServer 6.0 Service Pack 4 installed. I have deployed a web application using the wdeploy command line. I have defined an additional document directory that is outside of the web application and document root. No matter how many ways I try it, it seems to expect that the document root is the source of the files and totally ignores the additional document directory definition.
Example:
additional document directory: /add /opt/dir1/dir2
document root: /opt/doc/root
URL given: http://my.domain.com/uri/add/file.html
expected: to get file.html out of /opt/dir1/dir2
actual: fails, trying to get /opt/doc/root/add/file.html
Do additional document directories actually work? (They worked for us under iPlanet 4.1) If so, please tell me how to make them work with a deployed web application.
Thank you.
- Tom

In the original post you state:
Example:
additional document directory: /add /opt/dir1/dir2
document root: /opt/doc/root
URL given: http://my.domain.com/uri/add/file.html
expected: to get file.html out of /opt/dir1/dir2
actual: fails, trying to get /opt/doc/root/add/file.html
You are mapping /add to the new dir. The URL you would need to type then is:
http://my.domain.com/add/file.html
not
http://my.domain.com/uri/add/file.html
Mapping /add to a new dir will work. You do not need to specify /uri/add.

Restricted access to attachments in SRM 7.0 web applications

Hi,
We have a very specific problem regarding the handling of attachments with SRM 7.0 web applications. The system is configured to use ArchiveLink for storing documents on a remote content server, which is working fine.
Now we have a requirement which should restrict access to certain documents to specific user groups. As an example you could say that a Purchase order has (besides others) two documents attached, e.g.
- signed contract
- meeting minutes
The contract should only be visible to a limited number of people, whereas the Meeting Minutes are accessible to everybody.
Our problem is that apparently only one Content Category ("BBPFILESYS") is used by the SRM web applications for an upload. When granting authorizations on this content category, we cannot distinguish between contracts and meeting minutes anymore.
Comparing this with the config in ECC we can freely define document types which can be used in AUTH profiles. Is there any similar solution that can be used in SRM 7.0?
Any help would be greatly appreciated.
Cheers,
Mark

Hello,
Have a look at note 1334202. It provides some inputs.
Regards,
Ricardo

Problem restricting Integration Directory object access

Hi All,
We are trying to restrict access to a group of objects in the Integration directory. In the tab "Party" i select the option as follows:
Selection Paths -
Operator - Include, Party - Service without party, Service - BSR_TEST
Objects -
Operator - Include , Type = *, Action - Change
However, this role when assigned to the user allows create and delete option as well. Also, if any other role is assigned to the user and then revoked, the restriction does not work (the role mentioned above gives an Insufficient authorization error even for the objects it is set to permit)
Our XI system version is 7.0 with SP level 17.
Thanks in advance for your inputs
Vijaya

Hi Abhishek,
Thanks again for your response. However any ideas as to why the role would stop working f user settings are changed?
Also, when i select the service using option - single selection and select multiple checkboxes (even 2) it does not work, where as if i add 2 rows with one value it is ok.
Let me know if i am missing something
Thanks
Vijaya

How to restrict read access to certain document in stellent content server

Hi,
We are using stellent content server to store project documents. We would like to restrict access to certain confidential documents.
Users with Read / Write permission should not be able to access but admins with RWDA permission should be able to access these confidential documents.
Appreciate your inputs on this.
Thanks,
Nayana

Without seeing your setup and environment its a bit hard..
But...
Make sure that user has read only access to public security group.
You could setup an addition role with readOnly access and apply it those users.
Or restrict there account to have Read only access.
Remember if the user has Admin access on the Account but only readonly access on the security group then they will only have read only access on the files and visa versa.. :)
J.
Message was edited by:
JRS

Problems to restrict access to a page when the user belong to more than 1 group

I have realized that Dreamweaver on a coldfusion document only works fine when the user only belongs to a single group, this is because the code supplied by dreamweave when you use the option "Restrict access to a page" at "Server behaviors" it assumes that the user only have one group as you can see on this line created automaticly by dreamweaver:
<cfif MM_Username EQ "" OR MM_UserAuthorization EQ "" OR ListFind("admin",MM_UserAuthorization) EQ 0>
MM_UserAutorization has the value of the field assigned for the list of groups or levels, as you can see it could work if we reverse the parameters of the listfind function but the problem would be if we grant the access to more than one group because the sentence would be like this:
<cfif MM_Username EQ "" OR MM_UserAuthorization EQ "" OR ListFind("Admin,Manager",MM_UserAuthorization) EQ 0>
so both paramethers are lists therefore no user will get access to the page.
I am trying to make a work around to fix this problem but I don't know how to get the name of the page since the Application.cfc so I can validate the access to this page against tables on my database.
Does someone have a work around or a tip how to fix this problem?
Thanks in advance.
AG

Seems like you have a problem with your group names.ctxLdap.modifyAttributes(groupName,member);Ensure that the value of your variable groupName is a a valid distinguished name.
Note that an OU (organizationalUnit) is not a group. You do not add users to OU's, you create users in OU's.

Problem with Restrict Access to Page with access level using ASP

I'm using Dreamweaver CS3 with ASP-VBScript and an Access
database. The pages were created from scratch for this project,
using those tools all the way through.
I've created a login page, an admin homepage, and add, edit,
and list records pages for three tables. The login page uses the
Server Behavior "Log in User", all other pages use the Server
Behavior "Restrict Access to Page". All of these are based on an
Access Level.
Login seems to work correctly, and redirects to the admin
homepage. From the admin homepage, I can open any other page as
expected, and they initially display correctly. On the add and edit
pages, however,
submitting the form often results in getting logged out, but
not always.
Once this happens, I can log back in, but other problems will
sometimes occur during that second login session. Sometimes,
logouts will occur on pages that worked fine during the first login
session. Sometimes, another session variable that I've setup
manually will change when it shouldn't...as if there were two
values stored for my session variable, and reloading the page
changes to the other value.
This
post seems closest to my experience, but it doesn't look like
there was really an answer beyond "I had to fight with it for a bit
to get it to work":
I suspected that there is some problem with session settings
on the server. We have an almost identical tool on the same server
that was developed with an older version of DW that works more
reliably; it sometimes has problems with the initial login, but
never has a problem after that.
Has anyone experienced problems like this? Any suggestions
for what to check? I'm really pulling my hair out since it's so
unreliable...the kind of problem that goes away when you try to
show someone and comes back when they leave.

Hello,
I was thinking that all I would need would be the username, although username and paswsword would be more secure. There are about 50 users and no groups or levels. They are all equal ... same level.
The website is private and there is a general content area for all users and then there will be private areas for each user where proprietary documents will be held. I need to be able to ensure that user 'A' can only see the user 'A' pages, user 'B' can only see user 'B', etc.
I don't really understand what the Dreamweaver script is doing, but the overview sounded like it was the right tool to accomplish what I'm trying to do.
Any assistance greatly appreciated.
thanks.

Problems while accessing images outside the web document-root folder

Our application runs on Oracle application server on Linux. Facing problems while accessing images outside the web document-root folder. This works with changes in global-web-application.xml by including the <virtual-directory> tag. The same change does not work when done on Linux machine. It is unable to find the image. Please help in resolving this issue.
</locale-encoding-mapping>
</locale-encoding-mapping-list>
</web-app>
<virtual-directory virtual-path="/img" real-path="/home/eposuat/" />
</orion-web-app>
Code in the jsp:
<img width=700 height=700 src="/img/3.tif"></img>
<img width=700 height=700 src="/img/WB.gif"></img>

This is one of the least satisfactory aspects of site management in Dreamweaver, and several developers, including myself, have been pressuring the Dreamweaver team for some years to improve this. Who knows? They might eventually take notice.
The only way to do this at the moment is to create two site definitions, one nested inside the other. Set up the site definition normally based on htdocs as your site root. Then create a new site definition based on site. Dreamweaver will nag you that it can cause problems, but it won't actually stop you from doing it. The only potential problem is with site synchronization.
The problem with using site as the only basis for your site definition is that Dreamweaver automatically puts things like the Connections, Scripts, and other folders in the site root. So, everything ends up at the wrong level of the site hierarchy. Quite frankly, the whole thing is a bit of a pain. Dynamic site development was added to Dreamweaver only in version 6 (Dreamweaver MX), and no one had really thought through the need to store files outside the site root.

Help! php Restrict Access to Page() in dw cs5 problem

I have an admin.php page which takes me to other pages where i can update my info displayed on the website. All was working well until I added the restrict access to page behaviour. When i log in successfully, I am supposed to be taken to those update pages. If the log in is not successful, I am led back to the login page (the "restricted" page). However, even if I log in successfully, I am being taken to the "restricted" page when I try to access the update pages! I do not understand what is going wrong. Any help?

anb_newbie wrote:
I have a login page which either takes me to the update info page or will take me to the "restricted" page. The problem is even with a successful login, I am taken to the 'restricted' page.
How do you know the login is successful? If you're taken to the restricted page, it means that the login failed.
There doesn't appear to be anything wrong with the code you posted here. Possible reasons for the failure include getting the username or password wrong (they're usually case-sensitive). It's also possible that sessions haven't been enabled on your server, or that PHP can't write to the directory where sessions are stored.

Problem restricting access to additional document directory

Similar Messages

Maybe you are looking for