Go to WAM Installation Folder (by default /usr/evidian/lpf)
cd /usr/evidian/lpf
Change Directory
cd /ap2/bin/
Enter the below command
. envvars
Note
After the dot there is an espace
Execute the below command
gdb -c path_of_coredump_file httpd
Note
Some coredump file comes with compressed (may be on RHEL9) files, and in this case, you need to first decompress it using the Linux Tool, then analyse the Coredump file with the gdb -c path_of_coredump_file httpd command.
With following commands we can check WAM installation verification such as installation successfull , file customization , file ownership and mode.
Info
verify: to verify a WAM installation
[root@oracle bin]# ./lpfsetuputil -u verify
[root@oracle bin]# ./lpfsetuputil -u verify
-<I>-| The dbaapi initialization with the WAM Directory ldap://oracle.evidian.local:390/o=lpfRoot is successful
-<I>-| Verifying WAM installed under '/usr/evidian/lpf' ...
-<I>-| Loading checksum file '/usr/evidian/lpf/data/installed.txt' ...
-<I>-| There is no rollback file
-<I>-| Checking file existence ...
-<I>-| Checking checksum for files that are not customizable ...
-<I>-| Checking checksum for files that are customizable ...
-<I>-| Checking file ownership and mode ...
-<I>-| Processing files that need to be removed ...
-<I>-| All files have been successfully verified
Info
endinstall: to perform other operations done at the end of the installation
[root@oracle bin]# ./lpfsetuputil -u endinstall
-<I>-| Migrating Apache specific directives on WAM Authentication Servers ...
-<I>-| The WAM Authentication Server 'Built-in Authentication Server' already contains Apache specific directives for CORS
-<I>-| WARNING: You must check the specific directives for CORS for Authentication Server 'Built-in Authentication Server'
-<I>-| WARNING: New Specific directives for CORS should be:
-<I>-| WARNING: ## CORS directives
-<I>-| WARNING: Header unset Access-Control-Allow-Origin
-<I>-| WARNING: # adapt this directive in order to take into account the domains allowed in CORS
-<I>-| WARNING: # Example: SetEnvIf Origin "http(s)?://(.*.)?(test-pxp.frec.bull.fr)(:.*)?$" AccessControlAllowOrigin=$0
-<I>-| WARNING: # to allow all domains: http or https, any domain, any port :
-<I>-| WARNING: SetEnvIf Origin "http(s)?://(.*.)?(.*)(:.*)?$" AccessControlAllowOrigin=$0
-<I>-| WARNING: Header always set Access-Control-Allow-Origin %{AccessControlAllowOrigin}e env=AccessControlAllowOrigin
-<I>-| WARNING: Header always set Access-Control-Allow-Methods "*"
-<I>-| WARNING: Header always set Access-Control-Allow-Headers "X-Requested-With, Content-Type, Origin, Authorization, Accept, Client-Security-Token, Accept-Encoding, access-control-allow-origin, access-control-allow-credentials,Access-Control-Allow-Origin "
-<I>-| WARNING: Header always set Access-Control-Allow-Credentials true
-<I>-| WARNING:
-<I>-| WARNING: ## CIAM directives
-<I>-| WARNING: Header always set X-Frame-Options SAMEORIGIN
-<I>-| WARNING: # CIAM allowed domains must be identified, others must be rejected
-<I>-| WARNING: # adapt this directive in order to take into account the allowed domains
-<I>-| WARNING: # by default all domains are allowed
-<I>-| WARNING: # Example: SetEnvIf Referer "http(s)?://(.*.)?(test-pxp.frec.bull.fr)(.*)?" ALLOWEDORIGIN=1
-<I>-| WARNING: # Comment the two following lines if you do not use the CIAM Connect JS SDK
-<I>-| WARNING: SetEnvIf Referer "http(s)?://(.*.)?(.*)?" ALLOWEDORIGIN=1
-<I>-| WARNING: Header always unset X-Frame-Options env=ALLOWEDORIGIN
info
WAM Version Check
[root@oracle bin]# ./lpfversion
WAM 9.0.10.8 (10359/240709163727) installed on oracle.evidian.local:/usr/evidian/lpf
LDAP schema version is 2.109
Provisioning Web Service version is 8.6.6
Portal JSP Welcome Server is Apache Tomcat/8.5.35
Welcome page server version is 4.1
Authentication server version is Apache/2.4.58
Security gateway version is Apache/2.4.58
Options:
-f: never check peer certificate with LDAPS
-d <trace level>: the trace level
-w <password>: old password for certificate database
-l: for a deferred operation
-b: for a background process
-t <tempo>: temporization in seconds
-p <ppid>: the parent process id
-u <admin server URL>: the URL of the Admin Server
-i [yes|no]>: does use IP listen ?
[root@oracle bin]# ./lpfadmin -status
http://oracle.evidian.local:9119 started
[root@oracle bin]#
On Windows: C:\Program Files\Evidian\EWAM\config\localization
On Linux: /usr/evidian/lpf/config/localization
Under the localization folder we can see all types of language files such as eua.en,eua.fr and many more.
Uncomment the lines below only if files (eua.en, eua.fr) are modified under localization.conf
# EuaResourceFile en config/localization/eua.en
# EuaResourceFile fr config/localization/eua.fr
# EuaResourceFile ja config/localization/eua.ja
EuaResourceFile en config/localization/eua.en
EuaResourceFile fr config/localization/eua.fr
EuaResourceFile ja config/localization/eua.ja
4. Now override existing messages in a given language and you can comment on previous messages and add new messages corresponding to the Key ID.
# From sg/htmlerrors/errors/text401Reason31.html.fr
# LPF_MSG_EUA_174: Votre compte a été verrouillé,\nsoit après un trop grand nombre d’échecs d’authentification,\nsoit par décision de l’administrateur.
LPF_MSG_EUA_174: Votre compte a été verrouillé, soit après un trop grand nombre d’échecs d’authentification, soit par décision de l’administrateur.
# From sg/htmlerrors/errors/text401Reason31.html.fr
#LPF_MSG_EUA_175: Pour faire déverrouiller votre compte, veuillez contacter votre\nadministrateur.
LPF_MSG_EUA_175: Veuillez patienter 20 minutes puis réessayer de vous authentifier. À la suite d’une réinitialisation du mot de passe, ce délai doit aussi être respecté.<br />\n<br>Dans le cas où le verrouillage persiste, nous vous invitons à prendre contact avec le service d’assistance compétent :<br />\n- Support Pharmaciens : `0122333122333<br/>\n- Support Conseillers / Utilisateurs : Numéro interne
Where :
s_client: to check the SSL communication with a Web Server, using the command: openssl s_client
The other options are used only for some utilities:
-e <port|url>: to specify the port or url to be used with`the 's_client' utility.
May have one of the following form:
- NULL or empty: use the LDAPS port found in lpf.conf
- <port>: to specify the ldaps port of the PXP directory
- <host>:<port>: to specify a remote ldaps server
- <ldaps|https>://<host>:<port>: full URL of a SSL web server
By using Web Access Manager Password Policy, you can define rules regarding the
modifications of Primary Account passwords and set the Primary Accounts lock out
policy.
You can also set one primary password policy per User Directory.The Built-in Password Policy in the object is created when Web Access Manager is installed.
You can either use this object or create new Password Policy objects.
WAM Password Quality
The Password Quality objects allow you to define the format of the passwords that
should meet your password quality requirements. Upon the installation of Web
Access Manager, a Built-in Password Quality object is automatically created. You
can either use this object or create new Password Quality objects.
Managing Characters Sets
To meet your password quality requirements, you can use different character set,
through the Web Access Manager characters sets objects. Upon Web Access
Manager installation, Characters Sets are automatically created. This enables you to
define immediately your password quality requirements, using the Password Quality
objects.
