New user proxy submission link click throws an error

[jaredgalanis]

I found one issue that I think probably exists already and that we may not be able to do much about or reproduce very easily.

I had a long-lived browser session where I was unable to successfully log out of PASS. When I tried a new user proxy sub and clicked the link in the email, the application threw an error when loading the submissions detail page.

The error appears to be a 413 coming from one of the elastic search queries on the submissions detail route model hook, but it's unclear why this would happen in some cases and not in others.

https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

I could not repro this in a fresh Firefox window and I also can no longer reproduce it in Chrome after having quit the application entirely.

Given an inability to reliably reproduce this when freshly authenticated, I think likely has to do with some quirks of our authentication strategy that we don’t control.

I will continue to monitor it and will write an issue for it, but after speaking with @jabrah , neither of us believe this is tied to the Octane upgrade branch work.

[jaredgalanis]

There is actually also a different manifestation, which may be an entirely separate issue, that occurs when clicking a new proxy user submission link.

In this error the user service is unable to match the new proxy user email with the submitter email on the submission (in this case it complains about nullness).

I have most reliably reproduced this error when fully logged out of PASS and attempting to visit the link.

@esm here is the har file we discussed (github made me zip it to attach here):

demo.pass.library.jhu.edu.har.zip