"Access forbidden" (HTTP 403) page displayed as dead end

[brainchild0]

When a web browser holding a login session as a regular user accesses an address corresponding to restricted site content, such as that available only for administrators, the server generates a HTTP 403 code and a displays page (e.g. "Access forbidden", "Logged in user must be an admin"). The page includes a footer, which features a configured external link, but no link for reaching the site content accessible to the user.

Suggested is inclusion on the page of a link to the user's main entry point into the application. The link might be given as a new text block, as the existing logo image, or both.

[joshtrichards]

Hi @brainchild0 - That link at the bottom can be adjusted to point at / (i.e. the login page) of the NC instance. By default it points at Nextcloud, but that's unnecessary. It's configurable under Administration->Theming. Is that not sufficient?

https://docs.nextcloud.com/server/26/admin_manual/configuration_server/theming.html

[brainchild0]

I will refrain from offering a judgment about whether the workaround is sufficient.

I feel that allowing an empty value would improve flexibility and usability, even if the effect of leaving an empty value would be that the system would generate the link following the scheme given in your suggestion of setting the value to /.

However, I feel that a better design would be one allowing the hyperlink to be omitted from the generated presentation.

As a broader matter, I feel the current field definitions carry a conceptual problem.

The footer is currently defined such as to feature the text of the configured name as a link for the configured address. As would be interpreted by the user, the assumption is that both the name text and the web address correspond to some particular external organization name and site.

I feel such assumptions are too restrictive to accommodate general use.

For example, if the text field might be given as ending in "Cloud Storage", rather than being simply the organization name, then the assumed conceptual relations would be invalid.