Solutions to keep the fragment when using Cryptgeon behind an OIDC Auth.

[rcosperec]

Hello,

Problem
Currently, if using an OIDC auth in front of Cryptgeon (such as Okta), if the user is not logged in, it will loose the fragment that was shared with the link, per the very nature of the URI Fragment.
The workaround is to reclick on the shared link so it's not blocking per say.

Proposed solutions
I think it could be interesting to implement a way of managing OIDC State for this. From my understanding, the way it works does comply with an all client-side application, however I'm not sure it fits in the scope of this app.

Also maybe there's a workaround/config that would allow this and I missed it.

At minimum, could it be possible to custom the "click below to show and delete the note if the counter has reached its limit" message?

Thank you!

[laitco]

+1

Would be nice to have the view/download under one URI configurable with all it´s needs to lockdown the rest (upload, create, etc.)