[DOCU-1003] Improve "Activation security" and summarize activation issues Created: 24/Apr/17 Updated: 03/Jul/17 Resolved: 18/May/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Martin DrĂ¡pela |
| Resolution: | Done | Votes: | 1 |
| Labels: | core | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Sprint: | Docu Sprint 23, Docu Sprint 24 |
| Story Points: | 2 |
| Description |
|
3 Tasks which are related: Improve the page Activation securitySlightly adapt the page Activation security.
Both mechanisms - if misconfigured - can lead to activation errors. Create a new page "Activation errors"We already have the page Handshake information for activation was incorrect in the Troubleshooting section section. This pages handles an issue due to misconfigured Magnolia activation key (#1 of the above mentioned mechanisms).
Create a new page "Known activation issues due to misconfiguration" (or something similar), it should list the 2 issues related to SSL as described by Viet plus the issue due to Magnolia activation key misconfiguration described on the page "Handshake information for activation was incorrect". Adapt the cross page links accordinglyLinks can / should be on these pages:
*) The last mentioned page may or may not "survive" if we introduce a new page |