pasman create -m does not update password in pasmgr.properties

When creating an instance with the following command :

proenv> pasman create -v -p 9910 -P 9911 -s 9912 -m tomcat:something -Z prod oepasprod

the default password for tomcat is still automatically registered in pasmgr.properties:
webPassword=243d22243331

This will return the following error when trying to access/manage the instance from the OEM:
The oemanager web application is not accessible: Server returned 401 for https://localhost:9911/oemanager/applications. (17899)

This is expected behaviour.

The PASOE product is not aware of the OEE/OEM and would not open a backdoor to an instance's remote administration by recording a password that anyone who logs into OEE/OEM can use to control the instance.

General security requires the client of the remote administration to 'know' the Tomcat account and password. Therefore the pasmgr.properties contents must require the human to 'know' that account and password and authorize OEE/OEM to use them.

The default for PASOE is that the OEE/OEM is optional and is treated as a separate user login, that is no different than any other remote administration tool console.

To set the OEE/OEM Management user credentials, refer to Article:

•  OEM: Where to set up the OpenEdge Manager user for PASOE  

It was determined that the Progress Product is functioning as designed.

An alternative option for which an Idea could be submitted, could be to have a 'secure' solution in a distributed network environment such as using AD for both OEE/OEM and PASOE instances ( with AD as a secure single point of user account and password control ).
Then the OEE/OEM login IS the PASOE instance login for remote administration.

For detailed information on how to submit an Idea, please refer to Article How to submit an idea for a Progress product enhancement.