cancel
Showing results for 
Search instead for 
Did you mean: 

Handling session timeout during Service Call

kammaje_cis
Active Contributor
0 Kudos

Hi experts,

I would like to understand what happens when a session timeout happens when a service call is made.

For example, I am idle in the Fiori launchpad for long time, and the session has timed out, and now I click on one of the tiles. This is what I see in my system.

-> A request is made to an OData service and it returns a 403 forbidden error

-> Immediately another call is made with the same URL but with URL parameter xhr-logon=iframe.

     This returns a "302 moved temporarily" and provides the login page's URL in response header 'location'.

-> The login page's URL received in above step is opened in a pop-up as an iframe. (Background is still Fiori Launchpad).

I actually get an empty pop-up because my login provider (URL) comes with a response header X-Frame-Options=sameorigin

Any idea on how to solve this issue? Any ideas welcome.

Copying Fiori and Gateway forums.

Regards

Krishna

Accepted Solutions (0)

Answers (1)

Answers (1)

vijaybhaskarraju_vegesana
Active Participant
0 Kudos

Hi Krishna,

Did you resolve this issue? If yes please provide us some pointers.

We stuck with the same issue.

Thanks,

Vijay

Former Member
0 Kudos

Hi Vijay,

The 403 and 407 error messages appear to indicate that the root cause is the proxy credential information is not set properly.

2151518 - PowerBuilder 12.6 connect to a OData datasource fails

Could you please check this it might be helpful. Thank you

Regards,

Krishna

vijaybhaskarraju_vegesana
Active Participant
0 Kudos

Hi Krishna,

Thanks for responding.

Our issue is exactly similar to the one which you posted.

"The login page's URL received in above step is opened in a pop-up as an iframe. (Background is still Fiori Launchpad)."


We are seeing a blank pop up screen since batch request is executing with xhr-logon = iframe.


did this note 2151518 solved the issue? or did you do any changes in your gateway server ? or SAML team handled this issue?


Please provide your workaround.


Thanks,

Vijay