When creating a new Portal, the initial administrator password is limited to 28 characters. However, after the site is set up, there are no such restrictions when changing the password. Is there a specific reason for this initial limit? I've reproduced this in 11.1, 11.2, and 11.3.
@TimoT I don't know the specific reasons why there are limitations (i.e. character limit, no special characters other than period), but this password is used to as the admin password for Portal's internal PostgreSQL database:
I'd have to check the later releases, but in earlier versions of Enterprise, when you attempt to migrate a Enterprise to a new set of servers using the webgisdr utility, the new Enterprise environment must have the same password for this internal database for the webgisdr to import successfully.
Thanks @JakeSkinner.
When I change the Portal PSA, I've also made it a habit to change this underlying portal postgres database admin password to match.
After the Portal site is setup, I'm able to exceed the initial 28 character limit for this database password too.
I have heard that the internal PostGreSQL password does not actually change when you change the Portal password afterwards - hence why you are able to exceed the 28-character limit. Somebody better versed in the internals of Enterprise can probably give a better answer.
Hi @waterschapVallei_en_Veluwe
You're right - changing the Portal PSA password afterwards does not change the internal postgres database admin password. However, going to portaladmin > system > database > update admin account will update the database admin credentials.
I have confirmed this updates successfully by running select queries against the Portal postgres database. I've also confirmed updating these credentials post-install can exceed 28 characters.