Révision 19b58bab
Ajouté par Remy Menard il y a presque 12 ans
| ETa/EpcisPHI/README | ||
|---|---|---|
|
Dependencies:
|
||
|
IoTa modules:
|
||
|
- LibXACML-EPCIS
|
||
|
- ETa-Client
|
||
|
- User-Client
|
||
|
libraries:
|
||
|
- commons-codec
|
||
|
- servlet-api
|
||
| ... | ... | |
|
IoTa-Installer installs and configures EpcisPHI.
|
||
|
(xacml_configuration.properties for the client library LibXACML-DS,
|
||
|
commons-logging.properties and log4j.properties for the logs)
|
||
|
A user must use a public/private key pair to connect to the web interface.
|
||
|
IoTa-Installer can generate this keys. The public key have to be added to the
|
||
|
truststore of the server. DN (Distinguished name) needs to be similar
|
||
|
to the LDAP directory provided by the User service. To log to the web
|
||
|
interface as "superadmin" who manages user accounts, add this user
|
||
|
in this way.
|
||
|
Modify the tomcat-users.xml file of Tomcat to manage identity with TLS.
|
||
|
See the INSTALL file.
|
||
|
|
||
|
Usage Dependencies:
|
||
|
- ETa
|
||
|
- User
|
||
|
- an EPCIS
|
||
|
|
||
|
Usage:
|
||
Formats disponibles : Unified diff
Version 1.9
- use TLS for secured links
- SigMa is now fully functionnal
- completed documention
- a lot of bugs fixed!
- signature creation from the canonical form of the event
- signature creation using ECDSA algorithm
- signature is correctly verified
- manage the extension identifying the owner of the event
- if no identity is provided, the identity of the certificate is used
- access to the web interface of policy management is made by
certificate
- if no identity is provided, the identity of the certificate is used
- create and use certificates for TLS
- configure Apache Tomcat for TLS
- show SigMa library (SigMa-Commons)