{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 爷的心禁止访问 的问题《Why is using jhipster oauth2 stateful, and how to》','https://www.manongdao.com/q-1019923.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Using Jhipster (monolith, oauth2, with registry) forces our users to log-in every once in a while.
After searching a bit, we assume that it's because we have multiple instances of our monolith and sometimes the users get routed to different instances.
So I have 2 questions:
- Why does Jhipster implement oauth2 in a stateful way?
- How should we handle this, assuming we're staying with the current configuration?