Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Application Development with PAS for OpenEdge : Design and Implementation Considerations : Security considerations : PAS for OpenEdge session access
PAS for OpenEdge session access
You can publish entry points (remote procedure pathnames) that control access to a PAS for OpenEdge session at run time using the EXPORT( ) method on the SESSION handle. Publishing an export list limits the remote procedures that a client application can execute to those that you specify with this method. Because this is a run-time operation, especially over a bound session-managed connection, you can change the list at any time that your application requires, and you can reset the list to empty, allowing access to the entire set of procedures available from the current PAS for OpenEdge PROPATH setting.
However, setting this list applies only to the server session in which you execute the EXPORT( ) method. This means that you might have to manage the list differently in your application depending on the application model and binding of the connection.
Note: As this is a context management problem, the only way to effectively manage this kind of information for a session-free application is to maintain your own context database for it.
For more information on setting and resetting entry points in a server session, see Programming for the application model .
* Application model interactions
* How to set and reset an export list for each application model
* Session-managed application with a bound connection
* Session-managed application with an unbound connection
* Session-free application