| Anonymous | Login | 2024-04-23 07:57 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0021211 | ClearCenter | app-central-management | public | 2018-08-16 11:01 | 2018-10-30 19:49 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | have not tried | ||||
| Status | resolved | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 7.6.0 Updates | Fixed in Version | 7.5.0 Updates | ||||||
| Summary | 0021211: Save file sync key on initialization | ||||||||
| Description | Some apps, notably the Certificate Manager, need to have the files from the master sync-ed to the slave. This is done via clearsync's filesync plugin. When an app requests a filesync, a remote API request is sent to the master to verify a shared password. There's no guarantee the master will be available which is less than ideal. It would be better if filesync key request was part of slave provisioning. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-08-16 11:01 | user2 | New Issue | |
| 2018-08-16 11:02 | user2 | Status | new => confirmed |
| 2018-08-16 11:26 | user2 | Status | confirmed => resolved |
| 2018-08-16 11:26 | user2 | Fixed in Version | => 7.5.0 Updates |
| 2018-08-16 11:26 | user2 | Resolution | open => fixed |
| 2018-08-16 11:26 | user2 | Assigned To | => user2 |
| 2018-10-30 19:49 | user2 | Target Version | 7.5.0 Updates => 7.6.0 Updates |
|
Issue History |