Incorrect URL for Passphrase Resets Sent to Web Messenger Users
|Article:TECH201096|||||Created: 2012-12-21|||||Updated: 2013-01-02|||||Article URL http://www.symantec.com/docs/TECH201096|
The "Recover Passphrase" message template that is sent automatically by PGP Universal Server to Web Messenger users who have forgotten their passphrase and click on the "I lost my passphrase" link on the Web Messenger login page can contain an incorrect URL. This is particularly likely to occur if PGP Universal Server has been upgraded from a previous version.
The URL is in the format:
where host.internal.dom is the value in the Hostname field under System / Network of the PGP Universal Server administrative interface.
Accessing the PGP Universal Server command line for read-only purposes (such as to view settings, services, logs, processes, disk space, query the database, etc) is supported. However, performing configuration modifications or customizations via the command line may void your Symantec Support agreement unless the following procedures are followed.
Any changes made to the PGP Universal Server via the command line must be:
- Authorized in writing by Symantec Support.
- Implemented by a Symantec Partner, reseller or Symantec Technical Support.
- Summarized and documented in a text file in /var/lib/ovid/customization on the PGP Universal Server itself.
Changes made through the command line may not persist through reboots and may be incompatible with future releases. Symantec Technical Support may also require reverting any custom configurations on the PGP Universal Server back to a default state when troubleshooting new issues.
The ext_hostname column of the cluster_member table in the database contains a value based on the Hostname of the server rather than the public URL used by Web Messenger.
To check whether the ext_hostname column of the cluster_member table is incorrect, run the following command:
psql oviddb ovidr -c "SELECT host, ext_hostname FROM cluster_member;"
If the ext_hostname value is incorrect, it can be corrected by contacting Support.
Article URL http://www.symantec.com/docs/TECH201096