Topic on Extension talk:VisualEditor

Issue is a symptom of: https://www.mediawiki.org/wiki/Topic:V2qh378y0tj83so8

Is VE designed to help users in the situation where the MW application is using an SSO auth with an time-out? This scenario creates two situations:

1. timeout prior to launching VE edit
2. timeout prior to work being saved in VE

In Case 1 - I see this VE error:
In Case 2 - I see this VE error:	ooui-dialog-process-error

So the question is - Is VE designed to help users resolve the scenario where the underlying auth has expired and they need to renew it in order for VE to work.

I get a very similar error when trying to use the VisualEditor:

Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 28) Timeout was reached. Would you like to retry? (Sorry, I don't know how to attach images.)

My wiki is https enabled and hosted on a Debian machine on Google Cloud. I have installed all packages that are suggested such as curl, openssl, parsoid, nodejs, etc, and have configured them as directed by the VisualEditor page, and set up all of the firewall rules suggested.

For me the problem is clear, after the session times-out, the page is no longer able to communicate with the parsoid service on the server. If only I could add a custom link to the VE system message.

What kind of SSO are you using? I have some experience with a network based authentication using the kerberos protocol, if that helps.

It's a SAML-based auth. Implemented with Meza [1]

[1] https://www.mediawiki.org/wiki/Meza

I don't think there is a way to inject a link into the error message. Maybe you could write a Gadget that detects a session loss (by pulling the web API every few seconds) and displays a modal dialog / overlay that asks the user to re-login.

so, my basic question is, "Is VE designed to 'help' users work through a session loss scenario?" .. I'd like to hear a definitive answer on that from one of the VE project folks (Is that you?).

Base MW is fine wrt my SSO session loss. MW source edits renew well, form page edits renew well.. it seems that VE simply doesn't know what do do when the session needs renewed and it's frustrating because the solution is so simple. Ideally VE would just have a button that says, "renew session?" that does a silent and benign call to load.php and if successful, retrys the save.

But before I go down the rabbit hole of trying to implement a work-around, I'd like to know if my basic scenario is one that the VE project team has considered.