[GeoNetwork-devel] Problem with multinode geonetwork

Hi Devs,

I know there are discussions in progress to deprecate multinode geonetwork in the near future, but I have a strange issue that is causing me a number of problems, and I’d really appreciate knowing if there’s a work-around.

I know there are problems authenticating multiple nodes in the same browser, although I don’t know the details of this. When I work with multiple nodes myself (for testing purposes and so on) I work around the node change warnings, or use an incognito window, or simply edit the URL to point at the correct node. However I’m finding very inconsistent behaviour in the menu items- sometimes these switch to the correct URL and sometimes they remain pointed at the default URL. Generally the admin console seems to work correctly, whereas the other menu items do not.

I can work with this but I have a client that is now using a non-default node, having previously used the default, and they are limited to IE11 as the browser. This problem with the menu items not pointing at the correct node seems even worse in IE11- I can replicate this myself.

Is this a known problem, if so- what is actually happening? Is there a work-around for IE11 users? Is there an actual bug that could be fixed, as we may be able to pay for this to be done as it’s quite important for us.

Many thanks

Jo

Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009

Sign up to our mailing list for updates on news, products, conferences, events and training

Astun Technology Ltd, The Coach House, 17 West Street, Epsom, Surrey, KT18 7RL, UK
t:+44 1372 744 009 w: astuntechnology.com twitter:@astuntech

iShare - enterprise geographic intelligence platform
GeoServer, PostGIS and QGIS training
Helpdesk and customer portal

Company registration no. 5410695. Registered in England and Wales. Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no. 864201149.

Hi Jo,

Le lun. 21 janv. 2019 à 18:30, Jo Cook <jocook@anonymised.com> a écrit :

Hi Devs,

I know there are discussions in progress to deprecate multinode geonetwork in the near future, but I have a strange issue that is causing me a number of problems, and I’d really appreciate knowing if there’s a work-around.

I know there are problems authenticating multiple nodes in the same browser, although I don’t know the details of this

Basically the main reason (I think) is that you have one user session in the browser for the web application. As the multinode mode is only one web application serving all nodes it does not handle multiple user sessions (would be one per node). The multinode “filter” only set the application context corresponding to the node (ie. which database to use - in short) for the session.

. When I work with multiple nodes myself (for testing purposes and so on) I work around the node change warnings, or use an incognito window, or simply edit the URL to point at the correct node. However I’m finding very inconsistent behaviour in the menu items- sometimes these switch to the correct URL and sometimes they remain pointed at the default URL. Generally the admin console seems to work correctly, whereas the other menu items do not.

Not sure what would be the issue, all links should be relative on the client side so they should not contains ‘srv’. I would check in
https://github.com/geonetwork/core-geonetwork/blob/master/web-ui/src/main/resources/catalog/js/CatController.js#L467
which detect the node and
https://github.com/geonetwork/core-geonetwork/blob/master/web-ui/src/main/resources/catalog/components/utility/CORSInterceptor.js#L50

which makes API calls.

I can work with this but I have a client that is now using a non-default node, having previously used the default, and they are limited to IE11 as the browser. This problem with the menu items not pointing at the correct node seems even worse in IE11- I can replicate this myself.

Is this a known problem, if so- what is actually happening? Is there a work-around for IE11 users? Is there an actual bug that could be fixed, as we may be able to pay for this to be done as it’s quite important for us.

No suggestion for a fix here, sorry.

Francois

Many thanks

Jo

Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009

Sign up to our mailing list for updates on news, products, conferences, events and training

Astun Technology Ltd, The Coach House, 17 West Street, Epsom, Surrey, KT18 7RL, UK
t:+44 1372 744 009 w: astuntechnology.com twitter:@astuntech

iShare - enterprise geographic intelligence platform
GeoServer, PostGIS and QGIS training
Helpdesk and customer portal

Company registration no. 5410695. Registered in England and Wales. Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no. 864201149.


GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Hi Francois,

Thanks for the quick response. I need to test this further by finding a copy of IE11 that has never visited the geonetwork installation at all, but the problem I’m having is that even after closing the default node, closing the browser, clearing all the internet files and cache, restarting the computer, it still defaults to showing the the default node URLs. I’ll dig into it further and look at those code links.

Thanks again

Jo

···

Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009

Hi Francois,

Just to close this off, it turns out that my nodes were missing some URL changes in the UI/config. The application URLs and node selector were set to use ‘srv’, and I had just missed this completely. I’m not sure if it’s a bug, since I’ve overwritten the original settings, so I’m happy to leave it for now, particularly as multinode is being deprecated.

Jo

···

Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009