Custom settings for public users

[will-moore]

See https://forum.image.sc/t/omero-webclient-link-to-web-app-only-for-non-public-users/116460

In that case the user wants different TOP_LINKS for public users.
There are lots of other use-cases where you might want different options for public users. E.g. download policy, web apps, open-with etc.

Thinking about this a bit, it occurs to me that it could be possible (as a new feature of omero-web) to create public overrides of each of the existing settings. So that you could do something like:

$ omero config append public.omero.web.ui.top_links ...

and then if a public user is logged-in, then omero-web would use these settings instead of the existing omero.web.ui.top_links etc.
This needs a bit more thought, but it would be nice to have one mechanism that handles this for all settings, instead of handling each setting in a different way...

[imagesc-bot]

This issue has been mentioned on Image.sc Forum. There might be relevant details there:

https://forum.image.sc/t/omero-webclient-link-to-web-app-only-for-non-public-users/116460/2

[sbesson]

There are lots of other use-cases where you might want different options for public users. E.g. download policy, web apps, open-with etc.

Just repeating what you said in https://forum.image.sc/t/omero-webclient-link-to-web-app-only-for-non-public-users/116460/2, if the aim is to provide a public access with different functionalities/features than the ones available under authenticated access, it should be possible to address this problem by deploying of a dedicated public-only OMERO.web application using the existing configuration properties.