Applying a global setting allowing the compilation of AppBuilder programs that reference encrypted files

This article describes a method for applying an XCODE-SESSION-KEY key to an AppBuilder program, allowing the compilation of encrypted source and include files.

Oct 28, 2015
Knowledge

Title

URL Name

Applying-a-global-setting-allowing-the-compilation-of-AppBuilder-programs-that-reference-encrypted-files

Article Number

000187240

Environment

Product: OpenEdge Version: All supported versions OS: All supported platforms

Question/Problem Description

When developing using the AppBuilder, where can the XCODE-SESSION-KEY (encryption/decryption key) be set , allowing the compiling of encrypted source and/or include files.

Steps to Reproduce

Clarifying Information

Some users prefer supplying encrypted files (source and /or include) to their customers, allowing those customers to (re)build the application but not have access to certain sensitive files. To facilitate this the XCODE utility can be used to encrypt source and/or include files.

The problem is, in cases where the Progress default key was not used to encrypt the files, the compilation process will fail with the error messages listed below. To correct these error messages and successfully compile with encrypted files, the XCODE-SESSION-KEY must be set to the key used to encrypt the encrypted files.

This article describes the method for defining the XCODE-SESSION-KEY in an AppBuilder application and allowing the compiling of encrypted source files and unencrypted source files that include encrypted include files.

Error Message

** Unable to understand after -- "<string>". (247) ** <program> Could not understand line <number>. (198)

Defect Number

Enhancement Number

Cause

Resolution

Compiling encrypted source files or including encrypted include files within AppBuilder, requires the XCODE-SESSION-KEY to be defined to the key used to encrypt the file(s). If the file(s) were encrypted using the default XCODE-SESSION-KEY then you don't need to do anything. If a non-default key was used then, to correct the syntax error described above, you need to set the XCODE-SESSION-KEY.

The XCODE-SESSION-KEY value is an attribute of the SECURITY-POLICY system handle. In order to set the SECURITY-POLICY's XCODE-SESSION-KEY you will be required to run a line of code in a procedure window within AppBuilder before compiling the code. The following steps describe how to perform this.

Start up AppBuilder.
Start->All Programs->Progress->OpenEdge->AppBuilder
Open a Procedure Window
Tools->New Procedure Window.
In the procedure window type the following:
SECURITY-POLICY:XCODE-SESSION-KEY = "<your xcode key>".
where <your xcode key> is replaced with the key that was used to encrypt the encrypted files. Remember that the key must be a character string and as such is enclosed in double quotes.
Click Compile->Run.

The XCODE-SESSION-KEY is now set for the entire session.

This method works both when executing the compile statement and when compiling or running from the AppBuilder.

Workaround

Notes

References to Other Documentation:
ABL Reference, Handle Reference: "SECURITY-POLICY system handle"

Keyword Phrase

Last Modified Date

10/28/2015 7:06 PM

Applying a global setting allowing the compilation of AppBuilder programs that reference encrypted files

Files(0)

Was this article helpful?

Was this article helpful?

Applying a global setting allowing the compilation of AppBuilder programs that reference encrypted files

Information

Related Articles