you will see a externalLoginKey=EL32757843547 this is time sensitive but is the mechanism for going between application. if your on a intranet not internet you lengthen the timeout. also look up <xs:attribute name="target-type" default="intra-app"> read the widge-*.xsd for documentation.
BJ Freeman sent the following on 10/26/2011 1:21 PM: > http://mail-archives.apache.org/mod_mbox/ofbiz-user/201007.mbox/%[email protected]%3E > > Bilgin Ibryam sent the following on 10/26/2011 9:29 AM: >> I see this question coming up regularly from time to time. >> Some times ago I explained why this behavior happens but cannot find >> my post right now. >> Also it should be fixed with OFBIZ-3862 long time ago, but there might >> be other corner cases that cause it. >> >> Basically what happened in the past was that every action that >> rendered a screen in the background (like an ajax call) invalidated >> externalLoginKey which is used to transfer the session between >> applications. And if you try to login to another application while the >> externalLoginKey is not valid, you get the login screen. >> >> If you can provide exact steps how to get, I'll take a look. >> >> Cheers, >> Bilgin >> >> On Wed, Oct 26, 2011 at 4:32 PM, Wai <[email protected]> wrote: >>> Hello All, >>> >>> Having logged in to use one ofbiz component, I have to perform another login >>> process whenever I make use of another component. I vaguely remember a >>> posting that mentioned that this is the way ofbiz works. Does anyone have >>> any tips to allow a user to login once and allow the user to access other >>> components (given that the user has permission to do so) without having to >>> go through the login process again? >>> >>> Thanks. >>> >>> -- >>> View this message in context: >>> http://ofbiz.135035.n4.nabble.com/access-to-different-component-requires-login-process-tp3941033p3941033.html >>> Sent from the OFBiz - User mailing list archive at Nabble.com. >>> >> >
