Export Log Files
From the SWS GUI is possible to export the log as a zip, by following these steps:
After the import has been completed, you start the virtual machine and configure the parameters via "Menu Console".
Image Removed
This menu permits to set parameters like proxy, NTP ecc. The options of this menu are:
- Register: VA registration to our centralized update system (SCM)
- Config: IP ADDRESS, GATEWAY, DNS and ROOT PASSWORD configuration
- Update: Updates installation (system and push updates)
- Proxy: proxy configuration NTLM and port
- Restart_jboss: restart of the application server SWS
- Restart_osad: restart of sync module VA/SCM
- Reboot: VA restart
- Shutdown: VA shutdown
- Logout: exit from Menu Console
- Exit: go to Bash shell*
*This option must be selected under the monitoring of a Namirial operator. Namirial doesn’t give any support about modifications executed without WEB interface or Console Menù
Register: SCM Registration and Updates
The VA SWS has the possibility of being associated to an updates released centralized system. The update modes will be released in two different modes:
- Channel Updates (updates available for all the VA who has signed in)
- Push Updates (updates sent directly to the specified VA)
The registration system provides the VA restart and the resulting hostname changing with the following scheme: NomeDelCertificatoDiFirma_ultime4cifreMacAddress. The maintenance of the hostname* is a prerogative to use the updates centralized systems (SCM).
Changing the hostname will not allow to the SCM system nor release the Push Updates service nor keep track of SWS releases and packs changes inside the VA. It is strongly discouraged to vary this parameter.
From MC it will be possible to launch the operation.
Functional Verification
Appliance SWS offer a GUI for test if signature and verify works correctly.
Try if signature device device works
Make sure that system works: start the virtual machine, open a browser on a workstation able to reach the machine and enter the following url:
http://<IP-APPLIANCE>:8080/SignEngineWeb/index.xhtml
A page as the one below will be shown:
Image Removed
Make sure that the signature system works properly:
Submit any document and drag it in the area below the box “File da firmare”.
Enter the following parameters:
- Dispositivo Assegnato: DEMO
- PIN: foo123
Click on “Firma”. If all is ok, the browser will propose to save the created signature
Check if the signature has been applied
SWS appliance at this link offer the web page dedicated for validate a signature, at this link:
http://IP-APPLIANCE:8080/SignEngineWeb/verify.xhtml
And follow this step for validate the file just signed:
- Click on "Seleziona file" and choose the file just signed
- Press on "Verifica"
At the end of validation, in otput will obtain this:
Image Removed
Don't worry about red cross, this caused by certificate associated to device name "demo" not enrolled by trusted Root CA.
The important messegge is: "Firma 1: DEMO NOME DEMO COGNOME" in the yellow rectangle.
Environment SWS
SWS is released with a default configuration that let carry out all necessary tests using a pre-development signature system by Namirial. Obviously the signatures obtained are affixed with certificates NOT issued by a Certification Authority accredited. Any verification of these signatures with third-party tools will report errors for unknown CA. If you want sign with certificate enrolled by trusted CA you should migrate from TEST to PROD configuration of SWS.
By default SWS is configured with TEST environment. At this link you can see the SWS configuration:
- Go to link:
- http://<IP-APPLIANCE>:8080/SignEngineWeb/help.xhtml
Like in this figure:
Image Removed
Below the step for migrate from TEST to PROD environment for SWS, is very easy you should upload only on file JKS which contains the certificates for connect to our system of signature.
Migrate from TEST to PROD environment
For migrate from TEST to PROD environment you should have received by mail the zip protected by password contains the JKS, the password zip has been delivered by SMS.
The steps are:
- Go to link http://IP-APPLIANCE:8080/SignEngineWeb/settings.xhtml
- Insert the password of SWS (see the section "Default Credentials") and press "Login"
- Go to tab "Impostazioni generali"
- Press on "Seleziona file" and select the JKS received by mail
- Press "Salva"
- Press "Riavvia server"
If the migration has been completed correctly, go to this link:
http://<IP-APPLIANCE>:8080/SignEngineWeb/help.xhtml
And you will see the label PROD (like in the yellow rectangle):
Image Removed
Appliance SWS offer tools for download log files and check if all connection (to namirial services) working correctly.
Log files
Below the list of files used by SWS:
Code Block |
---|
language | bash |
---|
title | Apache Reverse Proxy |
---|
|
/var/log/wildfly/signengineweb.log
/var/log/wildfly/tsl.log
/var/log/wildfly/server.log
/var/log/wildfly/boot.log
/var/log/wildfly/console.log |
To ensure continuity of service, the file older than 4 weeks will be automatically deleted.
Export Log Files
From SWS gui is possible to export the log as a zip. Following this steps:
- Go to link: http://<IP-APPLIANCE>:8080/SignEngineWeb/help.xhtml
- Press to "Esporta log"
At the end will download the zip files contains the log- Press to "Esporta log"
At the end, the zip file containing the log will be exported.