[MAGNOLIA-2056] Activation: 401s are ignored or not reported when activating a single page Created: 12/Feb/08  Updated: 23/Jan/13  Resolved: 03/Jun/08

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.5.4
Fix Version/s: 3.6

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLACTIVATION-60 Refactoring of activation components ... Closed
relation
is related to MAGNOLIA-2055 Activation should report an error whe... Closed
is related to MAGNOLIA-2127 New Cache features and api Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

If the subscriber is not configured to use the "form" authentication method while it should ("simple" not being supported on weblogic at the moment):

  • if trying to "activate including subpages", then the target instance reports a 401, and a alert box is opened on the author instance. That's correct.
  • if trying to activate a single page, then the problem is completely ignored and unreported.

This calls for 2 things:

  • consolidate the activation mechanism for single pages and "incl. subpages"
  • improve the error reporting from the target instance (see also MAGNOLIA-2055)


 Comments   
Comment by Jan Haderka [ 03/Jun/08 ]

Fixed as part of MAGNOLIA-2121

Generated at Mon Feb 12 03:32:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.