[
https://issues.apache.org/jira/browse/OFBIZ-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-4937.
----------------------------------
Resolution: Fixed
I reverted r1429273 at r1430207 and fixed again at r1430208 by backporting
r1068283 from trunk
> In version 10.04 - After clicking on lookup, display login page again
> ---------------------------------------------------------------------
>
> Key: OFBIZ-4937
> URL: https://issues.apache.org/jira/browse/OFBIZ-4937
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release 10.04
> Environment: Windows 7 Enterprise, OFBiz 10.04 on tomcat 6.x
> Reporter: Raghavendra Prakash
> Assignee: Jacques Le Roux
> Labels: file, java
> Fix For: Release Branch 10.04
>
> Attachments: LoginWorker.java, OFBIZ-4937 In version 10.04 - After
> clicking on lookup, display login page again.patch
>
>
> Flow:
> 1. Login to application product
> 2. Select product lookup
> 3. Select party application
> OFBiz displays login page again.
> Cause: externalKey becomes stale.
> I have fixed the issue with a small work around. Dont know how to update the
> code base for public use.
> externalLoginKeysWR - contains the userLogin for externalLoginKey from
> app-level tabs
> Logic behind: The userlogin could not be found for the external key after the
> lookup request handled
> by OFBiz. The external key with app level tabs become stale once the lookup
> request is handled, and userlogin
> was removed for app level tabs' external keys. As a work around, this fastmap
> still maitains association with that
> external key. When the userlogin could not be found with external key, it
> would be searched in this fastmap.
> This is accomplished in checkExternalLoginKey and getExternalLoginKey methods
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
