Bug 793634 - Change status message after updating LDAP readonly attributes
Summary: Change status message after updating LDAP readonly attributes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: mark yarborough
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard: EPP_6_0_0_Candidate
: JBEPP-713 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-08 08:57 UTC by Martin Weiler
Modified: 2018-11-14 15:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: JBEPP-713
Environment:
Last Closed: 2013-07-26 09:28:17 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-713 0 Major Closed Change status message after updating LDAP readonly attributes 2013-07-26 09:25:02 UTC

Description Martin Weiler 2010-12-08 08:57:40 UTC 
++ This bug is a clone of bug 793633 ++

Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005ezPA
project_key: JBEPP

After JBEPP-640 has been fixed, LDAP attributes marked as "readOnly" are no longer updated through the OrganizationPortlet. However, when I click the Save command, it says " The user profile has been updated". The information message is misleading because I marked all the attributes such as Firstname, Lastname, Email, etc as readonly and I think it should give a warning/error message saying that "the attributes are marked as readonly and can't be updated".
Comment 1 Martin Weiler 2010-12-08 08:58:17 UTC 
Link: Added: This issue is related to JBEPP-640
Comment 2 Martin Weiler 2011-02-10 14:26:30 UTC 
Help Desk Ticket Reference: Removed: https://na7.salesforce.com/500A0000004Tlc3 Added: https://na7.salesforce.com/500A0000005ezPA
Comment 3 boleslaw.dawidowicz 2011-03-24 08:54:59 UTC 
PLIDM just updates what can be and is not raising any kind of exception if there is readonly as part (which also could be stupid).  Any changes to have such behaviour would need special handling in the UI as there is no notion of readonly attribute there atm. So it needs a bit deeper rework of UI part + maybe some info exposure from idm layer.

There is no short/easy way to quickly add this atm.
Comment 4 Thomas Heute 2012-01-12 10:02:38 UTC 
Link: Added: This issue relates to JBEPP-467
Comment 5 Thomas Heute 2012-01-13 12:57:03 UTC 
Labels: Added: EPP_6_0_0_Candidate
Comment 6 Thomas Heute 2012-09-03 11:27:07 UTC 
*** Bug 793633 has been marked as a duplicate of this bug. ***
Comment 7 Boleslaw Dawidowicz 2013-04-17 07:31:26 UTC 
Too wide scope to work on it for 6.1 at this point
Comment 9 Boleslaw Dawidowicz 2013-07-26 09:28:17 UTC 
Design limitation. Not easy to fix and require reimplementing some parts.
Note You need to log in before you can comment on or make changes to this bug.