Demo meeting nr 2 » Historie » Verze 5
Jan Pašek, 2021-03-26 13:43
1 | 1 | Jan Pašek | h1. Demo meeting nr 2 |
---|---|---|---|
2 | 2 | Jan Pašek | |
3 | 3 | Jan Pašek | *Date:* 26.03. 2021, 14:00 |
4 | 2 | Jan Pašek | *Present:* David Friesecký, Michal Seják, Stanislav Král, Jan Pašek, Ing. Jakub Daněk, Ing. Petr Pícha |
5 | |||
6 | h2. Agenda |
||
7 | |||
8 | # Discussion about requirement specification document, based on the document sent at the beginning of this week. |
||
9 | # Building chain of trust via _Authority Info Access_ vs. using a certificate chain embedded in the PCKS#12 identity file. |
||
10 | # How does the YOSO application use our certificates to build PCKS#12? Shall we provide the PEM files with the whole chain included, or provide the chain as a separate file? |
||
11 | # Presentation of the Proof of Concept |
||
12 | # Presentation of the Web GUI proposal |
||
13 | # Brief introduction to the application architecture |
||
14 | |||
15 | h2. Conclusion |
||
16 | |||
17 | 4 | Jan Pašek | # The customer has found no problems with the requirement specification document. |
18 | # AIA is not required by the customer. The chain of trust (excluding the root) will be packed into the identity file. The root will be added as trusted in the Adobe Acrobat Reader |
||
19 | 5 | Jan Pašek | # The customer needs a possibility to download the certificate and an additional file including the whole chain without the root. All the downloaded files will have a PEM format. The application shall be ready to be extended to other download formats. |
20 | # A proof of concept was presented to the customer. The customer had no comments or change requests. |
||
21 | # GUI was presented. The customer expressed a requirement to avoid popups in the Web GUI for the sake of future support of mobile devices. Furthermore, possibilities to simplify the creation of the certificates were discussed. |
||
22 | # The architecture (Overall architecture view and Class diagram) was presented. The customer proposes an architecture simplification. However, the final decision responsibility is placed on the team. |