Skip to main content
S
simeon_mitev
Participant
November 14, 2007
Answered

User sessions

  • November 14, 2007
  • 1 reply
  • 1638 views
I have programmed an interface (web app) between external Event Management System and Breeze . Everything is fine until I experienced the problem with session expiration. When the software connects and login I keep BREEZESESSION and use it on every next request. The problem occurs when the application is not requested (and does not requests breeze) for longer time. It looks like the session expires and BREEZESESSION is no longer valid because I get:

<results>
<status code="no-access" subcode="no-login"/>
</results>

as response from the server.
Is it the only solution for this case to check the status of every response and if it is "no-access" then login and redo the request?
    This topic has been closed for replies.
    Correct answer simeon_mitev
    I will answer myself because I got the solution.
    The session expires after 16 hours. If you develop middleware which has to keep the state, check the 'status' code after each request sent to connect xml api. If the status is "no-access" then the session has been expired. Just login your application again and redo the request. that's it.

    1 reply

    S
    simeon_mitevAuthorCorrect answer
    Participant
    November 16, 2007
    I will answer myself because I got the solution.
    The session expires after 16 hours. If you develop middleware which has to keep the state, check the 'status' code after each request sent to connect xml api. If the status is "no-access" then the session has been expired. Just login your application again and redo the request. that's it.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices