Kbase P167863: How to control user access to WebSpeed development broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/06/2010 |
|
Status: Unverified
GOAL:
How to control user access to WebSpeed development broker
GOAL:
How to configure WebSpeed environment in order to restrict access to the development broker
FACT(s) (Environment):
All Supported Operating Systems
WebSpeed
Webservers
FIX:
In order to restrict user access to a WebSpeed broker running in development mode,
changes have to take place at the web server and WebSpeed messenger configuration.
WebSpeed broker does not have user authentication and authorization feature unless
that is implemented in the application code.
The process of restricting access to a WebSpeed development broker consists of 2 steps:
1. Configure new physical or virtual directory with permission to execute scripts and executables
and set user authentication and authorization using web server's tools. For Microsoft IIS
one can use Internet Information Services (IIS) Management Console, for Apache that would
be setting up configuration file with user authorization directives and/or .htaccess file.
Upon performing this step, WebSpeed messenger script (or executable) needs to be
copied into that physical or virtual directory.
2. Configure WebSpeed messenger script (or executable) to either:
a) Connect using separate NameServer that will be used as the controlling NameServer
for the WebSpeed development broker
or
b) Connect directly to the listening port of the WebSpeed development broker.