[MAGNOLIA-2692] When using ExternalUserManager user can not login to Admin Central Created: 02/Apr/09  Updated: 23/Jan/13  Resolved: 17/Apr/09

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.0.1
Fix Version/s: 4.1, 4.0.2

Type: Bug Priority: Blocker
Reporter: Tobias Bösch Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 4.0.1; java-1.5.0-sun-1.5.0.14-1jpp; Centos 5 32 bit


Attachments: Text File MAGNOLIA-2692.log.txt     PNG File Picture 11.png     Text File stacktrace.txt    
Issue Links:
relation
is related to MAGNOLIA-574 User preferences Closed
is related to MAGNOLIA-2400 Split Roles/Groups assignment from Us... 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   

I setup usergroup 'G-RTR-PMM-editors' with role 'acl' assigned. If I assign this group to a local JCR user (info.magnolia.cms.security.MgnlUserManager) this user can login to admin central (ie. is logged in and sees menu structure).

If I try to login with a active directory user using (info.magnolia.cms.security.ExternalUserManager) that has assigned the same group in AD, the user is logged in but processing of the page stops and a partial page is displayed.

Stacktrace attached.



 Comments   
Comment by Jan Haderka [ 03/Apr/09 ]

The problem was introduced when adding link to user preferences in the admin interface. For external users there are no editable preferences in the system and hence the link should be disabled.
I've deployed snapshot with possible fix at http://repo.magnolia.info/snapshots/info/magnolia/magnolia-module-admininterface/4.0.2-SNAPSHOT/magnolia-module-admininterface-4.0.2-20090403.092625-1.jar Can you download the snapshot, replace your current magnolia-module-admininterface-4.0.1.jar with it in your webapp and confirm that the issue is fixed? Thanks
If it fixes the issue for you, you can keep using the snapshot until proper fix is released. If you do so, and want to perform upgrade later, don't forget to change value of /modules/adminInterface/version node back to 4.0.1 just before the upgrade.

Comment by Tobias Bösch [ 03/Apr/09 ]

edited / moved logs to MAGNOLIA-2692.log.txt

Comment by Jan Haderka [ 03/Apr/09 ]

You get this exception only when you try to see admin central or even before?
I've deployed another snapshot that avoids failing call alltogether. Could you please try again with http://repo.magnolia.info/snapshots/info/magnolia/magnolia-module-admininterface/4.0.2-SNAPSHOT/magnolia-module-admininterface-4.0.2-20090403.105301-2.jar and if it doesn't work, please get on irc://irc.freenode.net/#magnolia-support as I'll have few more questions. Thanks.

Comment by Tobias Bösch [ 17/Apr/09 ]

Thanks Jan. This version works for me.

Comment by Jan Haderka [ 17/Apr/09 ]

Fixed on trunk as of r24418 and on 4.0 branch as of r24419.

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