Try OpenEdge Now
skip to main content
WebClient Applications
Deploying an Application : Customizing deployment configurations : Defining a custom deployment configuration : Security considerations
 
Security considerations
Customers who host WebClient applications developed by an outside application provider must coordinate with the provider to make sure security is properly configured. These customers also must instruct their end users to recognize and trust their digital signatures.
If the application provider makes the prowcdp.zip file available, the customer can run the Deployment Packager and manage the security settings and other settings independently. Alternatively, the customer may specify the requirements and ask the application provider to define the deployment configuration accordingly.
Working as necessary with the application provider, the customer must make sure that:
*Both the .prowcapc file and the .CAB files are signed if digital signatures are used. (You do not need to use the same certificate for both; either the customer or the provider can sign the files.) If one is signed and the other is unsigned, the application will not run. You can only specify the digital signature (or the absence of it) for the .prowcapc file with Deployment Packager. Typically, the application provider must make any required changes to the .CAB files.
*The authentication settings, as well as the URLs, are correctly specified for the Configuration File Locator and the Codebase Locator. Either the customer or the application provider can adjust these settings through the Deployment Packager.
*End users are properly informed how to respond to security prompts. For digitally signed files, you should instruct end users to trust content signed by either the customer or the application provider, as applicable.