Consultor Eletrônico

Using the Progress AppServer for Security with Export Table

INTRODUCTION
============
This knowledgebase entry gives an overview of using an
Export Table with the Progress AppServer for application
security.

EXPORT TABLE
============
An Export Table can be used to limit the procedures that can
be accessed by an application server. Export Tables are built
with the Export() method for the session by adding the procedures
and patterns specified to the Export Table when the method is called.
Only the asterisk is supported as a wildcard character when using
patterns. Refer to the MATCHES function in Language Reference Manual
for information on wildcard specifications.

There is no way to remove procedures and patterns from an Export Table
once they have already been added.

If an Export Table is not built for the application server, all
procedures accessible with the PROPATH can be called as remote
procedures.

EXAMPLE
=======
The following code would be run within the context of the
Progress AppServer (the -con procedure is an example of
where this could be done) to build the Export Table.

DEFINE VARIABLE ret AS LOGICAL.
ASSIGN ret = SESSION:EXPORT("total-orders.p,update-inventory.p").

The above puts total-orders.p and update-inventory.p into the
Export Table.

DEFINE VARIABLE ret2 AS LOGICAL.
ASSIGN ret = SESSION:EXPORT("update-address.p").

The above adds to the Export Table which results in
total-orders.p, update-inventory.p, and update-address.p all
being included in the Export Table.

Consider the following code being run on the 4gl client which is
connected to the Progress AppServer where the above Export Table
was built:

RUN update-inventory.p IN AppServerhandle.

The above will run successfully because update-inventory.p is
defined in the Export Table.

RUN update-names.p IN AppServerhandle.

This run statement will raise the STOP condition because
update-names.p is not defined in the Export Table.


Progress Software Technical Support Note # 16208