Révision 19b58bab
Ajouté par Remy Menard il y a presque 12 ans
| ETa/EpcisPHI/src/main/webapp/Login.jsp | ||
|---|---|---|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
|
||
|
<title>EPCIS ACCESS CONTROL CENTER</title>
|
||
|
<link rel="stylesheet" type="text/css" href="style/style_DS.css" />
|
||
|
<script type="text/javascript" src="script/check_form.js"> </script>
|
||
|
</head>
|
||
|
<body>
|
||
|
<h2>EPCIS ACCESS CONTROL CENTER</h2>
|
||
| ... | ... | |
|
}
|
||
|
%>
|
||
|
<div id="logForm">
|
||
|
<form method="post" action="RootAccountAuth?action=login" onSubmit="return verifFormLog(this);">
|
||
|
<span>login : </span><input class="inputText" type="text" name="login" value="" /><br/>
|
||
|
<span>password : </span><input class="inputText" type="password" name="passwd" value="" />
|
||
|
<form method="post" action="RootAccountAuth?action=login">
|
||
|
<div><input type="image" src="./pics/login.jpg"/></div>
|
||
|
</form>
|
||
|
</div>
|
||
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)