Overview
This guide is intended for allowing users with restricted access to have permission to access DSP pages which invoke webMethods services
Steps to Follow
User Creation
Create the user required via the Users and Groups page.
Group Creation
Create a group and add the above user to the group.
ACL Creation
Create an ACL and add the above group as well as the Administrators and Developers group to the ACL.
Now you have an ACL you can assign to services/pages which will only allow groups Allowed in the ACL to invoke services or see pages. Now assign this ACL to the folders/services and pages.
Service/folder ACL configuration
To allow a user to invoke certain services in a package the permissions can be set via the Admin Console or in the package itself. This guide will explain how to do it via the Admin Console.
Click on package management and then Browse Folder.
From here an Administrator user can assign ACL's at folder or service level.
Assign the appropriate ACL to the required folders/services.
.access file creation
To distinguish which pages the file server can serve to users .access files are used. These files basically list the pages for which permissions need to be set and a corresponding ACL to set for the page.
Create a .access file in the /pub directory of the package
For each dsp or html file the server needs to serve the user, add an entry in the .access file for the page and corresponding ACL. Below is an example:
index.dsp NewACL
handle1.dsp NewACL
handle2.dsp NewACL
handle3.dsp NewACL
handle4.dsp NewACL
.access file does not support directory structure by any means.
./directory/index.dsp NewACL - Not allowed!!
directory/handle1.dsp NewACL - Not allowed!!
handle2.dsp NewACL - Correct!!
To assign ACL to a page located in a sub-directory under /pub, a separate .access must be created and placed inside the sub-directory.
When editting a .access file, the package will need to be reloaded for the update to take effect.
Accessing the page
Now to access the dsp/html page specified open a browser and enter the following url with the appropriate details:
Then enter the new users details to the authentication prompt. The page should load correctly and any services which need to be invoked will inherit the permissions from the dsp authentication.
