PASOE security model is undefined if the instance is created via OpenEdge Explorer or the pasman/tcman command

In the PASOE conf/appserver.properties file, the psc.as.security.model property is empty when the instance is created via OpenEdge Explorer or via the tcman/pasman command utility.

Jan 14, 2020
Knowledge

Title

URL Name

PASOE-security-model-is-undefined-if-the-instance-is-created-via-OpenEdge-Explorer-or-the-pasman-tcman-command

Article Number

000132833

Environment

Product: OpenEdge Version: 11.7.4, 11.7.5 OS: Linux

Question/Problem Description

PASOE security model is undefined if the instance is created via OpenEdge Explorer or the pasman/tcman command line tools.

In the PASOE conf/appserver.properties file, the psc.as.security.model property is empty when the instance is created via OpenEdge Explorer.

In the PASOE conf/appserver.properties file, the psc.as.security.model property is empty when the instance is created with the PASMAN or TCMAN command utilities

psc.as.security.model property has no value defined when the instance is created via OpenEdge Explorer or the pasman/tcman command line tools.

pasman create -Z prod does not populate the appserver.properties psc.as.security.model value
pasman create -Z dev does not populate psc.as.security.model value in the appserver.properties configuration file

Steps to Reproduce

From the PROENV console: 1. Create the PASOE instance using pasman (alternatively you can use tcman, with the same outcome): $ pasman create -f -Z prod -p 10080 -P 10443 -s 10445 -N prod2 $WRKDIR/prod2 -v $ $dlc/servers/pasoe/bin/tcman.sh create -p 8082 -P 8447 -s 8446 -N testpas -f -Z dev /usr/pasoe/test 2. Query the new instance environment settings to grep the security model: proenv>pasman env -I prod2 | grep security security model: 3. Query the new instance configuration settings to grep the security model: proenv>pasman config -I prod2 | grep security -Dpsc.as.security.model=

Clarifying Information

When created with -Z prod, the new instance exhibits the expected default features of a Production instance with:

All transports disabled by default
srvrAppMode switched to production

Only -Dpsc.as.security.model is not populated with the correct value.

Error Message

Defect Number

Defect ADAS-16051

Enhancement Number

Cause

This was caused because the variables used to set psc.as.security.model were not properly capitalized.

Resolution

Upgrade to OpenEdge 11.7.6, 12.2 or later.

The fix for this issue is expected to be in the upcoming release 11.7.6. As of January 2020, release 11.7.6 is scheduled to be released in Q2 2020, although dates and content of the release are subject to change.

The fix for this issue is expected to be in the upcoming release 12.2. As of January 2020, release 12.2 is scheduled to be released in Q2 2020, although dates and content of the release are subject to change.

Workaround

Manually modify psc.as.security.model property in $CATALINA_BASE/conf/appserver.properties

Notes

Progress Article:

Differences between PASOE instances created with -Z prod under dev license and a real production instance

Keyword Phrase

Last Modified Date

11/20/2020 6:57 AM

PASOE security model is undefined if the instance is created via OpenEdge Explorer or the pasman/tcman command

Files(0)

Was this article helpful?

Was this article helpful?

PASOE security model is undefined if the instance is created via OpenEdge Explorer or the pasman/tcman command

Information

Related Articles