[ALF-486] Cannot login to Share with an empty last name Created: 06-Jul-09  Updated: 21-Jul-11  Resolved: 30-Mar-11

Status: Closed
Project: Alfresco
Component/s: Platform Authentication and SSO
Affects Version/s: 3.1 Enterprise
Fix Version/s: 4.0 Enterprise

Type: Bug Priority: Major
Reporter: mkononovich Assignee: Closed Bugs (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: 2 days
Time Spent: Not Specified
Original Estimate: 2 days

Testcase ID:

Rep-1085

Date of First Response:

 Description   

Trying to login to the Share with the LDAP account, that has no last name, I have an error 500 that was caused by:

"org.json.JSONException: JSONObject["

{http://www.alfresco.org/model/content/1.0}

lastName"] not found."

Our settings:

          • LDAP --------
            authentication.chain=ldap-ad:ldap-ad
            ldap.authentication.java.naming.provider.url=ldap://ad-server:389
            ldap.authentication.userNameFormat=%s@domain.com
            ldap.authentication.java.naming.security.authentication=simple
            ldap.authentication.active=true
            ldap.synchronization.active=true
            ldap.authentication.defaultAdministratorUserNames=admin-user
            ldap.authentication.authenticateFTP=false

#---LDAP-sync------------
ldap.synchronization.java.naming.security.principal=Listing@domain.com
ldap.synchronization.java.naming.security.credentials=Listing-pwd
ldap.synchronization.groupSearchBase=dc\=domain,dc\=com
ldap.synchronization.userSearchBase=dc\=domain,dc\=com
synchronization.synchronizeChangesOnly=false
synchronization.import.cron=0 0 0 * * ?
synchronization.syncWhenMissingPeopleLogIn=true
synchronization.autoCreatePeopleOnLogin=true

AntonRy



 Comments   
Comment by mkononovich [ 06-Jul-09 ]

Found in Alfresco 3.2 Community build 2034 using Windows 2003 SP1 x32, Tomcat 6.0.18, Mysql 5.1.34, JDK 6u14 x32, MS AD

Comment by Roy Wetherall (Inactive) [ 13-Nov-09 ]

Can we get some more information about where this error is being raised.

Im not in a position to reproduce with LDAP so with out knowing where this error is being raised it is hard to fix.

Comment by Alfresco QA Team (Inactive) [ 19-Nov-09 ]

If user in LDAP has it's attribute "sn" as a "", then it cannot login to the share.
During the sync this attribute "sn" should be mapped as ldap.synchronization.userLastNameAttributeName=sn due to config.
Cannot advise how to easily create sucha person in the Alfresco not using LDAP (GUI doesn't allow such users to be created).
It seems, that the error exists because of Share relies on that fact that the Last name always persists. But it's not so.

Comment by Roy Wetherall (Inactive) [ 20-Nov-09 ]

This won't be complete before freeze today.

Issue seems to be in the web script that is expecting all the elements of the name to be there. Still need more information about which web script this is.

Comment by Steve Rigby [X] (Inactive) [ 30-Mar-11 ]

Please retest in Swift (Alfresco 4.0)
If issue is not reproduced then please Close.
If still present then please Reopen with screenshot / log if issue reocurring.

Comment by Steve Rigby [X] (Inactive) [ 23-Jun-11 ]

Moving to QA Backlog

Comment by Steve Rigby [X] (Inactive) [ 04-Jul-11 ]

For retest in Swift build

Comment by Alfresco QA Team (Inactive) [ 21-Jul-11 ]

The issue is successfully validated on Alfresco Enterprise 4.0.0 (105a) Tomcat, PostgreSQL, Java (all installer deployed)
Client: WinXP, FF 5.0

Generated at Wed Sep 30 10:25:08 BST 2020 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.