Forum

1.17.2 user will be...
 
Notifications
Clear all

1.17.2 user will be automatically logged out

8 Posts
4 Users
0 Reactions
28 Views
Posts: 7
Topic starter
(@beon-it)
Member
Joined: 6 years ago

Hi togehter,

since V1.17.2 we faced with the issue that a user that is logged in into the user frontend will be suddenly logged out.

So when a customer/user is logged in in his customer area to view all the tickets and he clicks on "Profile" for example,
then the session expired suddenly and the user has to login again.
This behaivor we also see when the user create a new ticket

So any hint on this would be appreciate!

Regards, Norman


7 Replies
Posts: 9
(@kleins)
Member
Joined: 6 years ago

Same here .. would be nice if someone could help


Reply
Posts: 1177
Admin
(@stevland)
Member
Joined: 2 months ago

To be honest this sounds like an vanilla osTicket issue, not anything to do with osTicket Awesome.

I'm willing to try and sort out if that's the case or not. But I can't seem to reproduce this issue in the osTicket Awesome client demo. Can you?

Are either of you guys using OAuth2 by chance?

 

 


Reply
Posts: 9
(@kleins)
Member
Joined: 6 years ago

Hey Stevland, 

tested with OAuth2. Same problem.
Only happens (here) when Users edits tickets in the frontend and tries to save them.
Then you get back to the login screen and it looks like you have to log in again. If you hit refresh on your keyboard you are still logged in... 

Sincerely


Reply
Posts: 1177
Admin
(@stevland)
Member
Joined: 2 months ago

The reason I asked if you're using OAuth2 is that what you have both described sounds like this issue:

https://forum.osticket.com/d/102248-microsoft-oauth-returning-to-homepage-without-user-logged-in/22

I can't really help you with this (other than pointing you in the right direction) as I don't use OAuth2 myself, and as this issue doesn't have anything to do with osTicket Awesome it is way beyond the level of support I can offer.

I will mark this as 'Resolved', but you can still comment if you feel that I've made a mistake.

I hope you get this sorted out soon. Good luck.


Reply
Page 1 / 2
Share: