View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009826 | 10000-012: Discovery | Spec | public | 2024-09-10 12:47 | 2024-10-07 05:20 |
Reporter | Matthias Damm | Assigned To | Randy Armstrong | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Product Version | 1.05.04 RC1 | ||||
Target Version | 1.05.04 | ||||
Summary | 0009826: Handling of ApplicationIdentity and certificate content changes | ||||
Description | The ApplicationConfiguration allows the change of ApplicationIdentity that mainly defines the content of certificates. Changes affect the certificates but 7.10.19 ApplicationIdentityDataType defines: How does a client create a new self-signed certificate if the server should continue to use a self-signed certificate? Or maybe there should be one endpoint with CA signed and one with self-signed. I am not aware of a option to tell the server to create a new self-signed certificate. We need more details on when to use the new information and how to trigger creation of new certificates. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-09-10 12:47 | Matthias Damm | New Issue | |
2024-10-07 05:20 | Randy Armstrong | Assigned To | => Randy Armstrong |
2024-10-07 05:20 | Randy Armstrong | Status | new => resolved |
2024-10-07 05:20 | Randy Armstrong | Resolution | open => fixed |
2024-10-07 05:20 | Randy Armstrong | Note Added: 0021838 |