[MAGNOLIA-3733] ExternalUser could implement getProperty Created: 09/Jun/11  Updated: 23/Dec/11  Resolved: 20/Dec/11

Status: Closed
Project: Magnolia
Component/s: core, security
Affects Version/s: None
Fix Version/s: 4.4.6, 4.5

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLLDAP-49 Pass on email and other user properti... Closed
relation
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)

 Description   

Depending on the login module, some properties are passed along when a user is logging in from an external system (see for instance MGNLLDAP-49). Maybe ExternalUser could return the property value if it knows about it.



 Comments   
Comment by Magnolia International [ 09/Jun/11 ]

Consider using the patch in MGNLLDAP-49; do we want to throw UnsupportedOperationException when the property doesn't exist ? (it's unclear why ExternalUser was doing that in the first place)

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