1. Set the value attribute of the enabled property as true.
2. Validate the ClientPrincipal token against domains:
For validating the token against a single domain, set the domain access code as the value attribute of the key property. The domain access code can be clear text or in the oech1::<hex-string> format.
You can generate the <hex-string> using the genpassword utility. For more information about the genpassword utility, see OpenEdge Getting Started: Installation and Configuration.
For validating the token against multiple domains:
1. Create a domain registry file using the Generate Domain Registry gendomreg.bat utility that is located in the $DLC\bin folder.
2. Uncomment the registryFile property in the OEPreauthfilter bean code.
3. Set the value attribute of the registryFile property as the output file name generated by the gendomreg.bat utility.
Note: If you set values for both key and registryFile properties, the ClientPrincipal token is validated against multiple domains that are specified by the registryFile property value. To validate the token against a single domain, comment out the registryFile property in the OEPreauthfilter bean code.
For validating the token against a single domain, set the domain access code as the value attribute of the key property. The domain access code can be clear text or in the oech1::<hex-string> format.