> > > > We have following concern with the above suggested approach. > Say we make the call1 and then receive the response 1 as the session still > exists. But between the time that we make the call2, session gets expired. > (since these are network calls and delays may occur.) > So at that point we face the same original problem again. > > Isn't the proper approach is to send a logout response from the identity > side with a proper message (no session exists) to the application side > rather than breaking the flow in the middle? > @IS Team,
Can you please share your thoughts on this and any fixes if needed please :). > > Senior Software Engineer, > WSO2 Inc. : wso2.com > Mobile : +94718184439 > Blog : http://tanyamadurapperuma.blogspot.com > -- *Ruchira Wageesha**Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: ruch...@wso2.com <ruch...@wso2.com>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
