Feature #27

Credentials are not applied when root level of a WMS is selected

Added by Mérour Xavier almost 11 years ago. Updated about 5 years ago.

Status:NewStart date:12/04/2008
Priority:LowDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Sponsor: Ergonomic impact:
Functional impact:

Description

Case : under Gaïa, the user can add a WMS service and then select either :

- the layers he would like to get
- the root of the service

In this last case, the layers he gets are not restricted to the one he can (has the right) to see but ALL the layers available on the remote WMS server.

It seems to be a major issue... and should be fixed as soon as possible (we have two WMS in production).

PS : same problem might occur with WFS ? we did not check

History

#1 Updated by Michaelis Renaud almost 11 years ago

  • Assignee set to Michaelis Renaud

As we keep the hierarchy of the layers, the root layer should be visible in order to be able to display the child layers.
To bypass this issue, just set the minimum scale and the maximum scale to 0. Thus the layer hierarchy will still exist but the root layer will be never displayed.

This problem should not appear with WFS.

#2 Updated by Magoni Bruno almost 11 years ago

  • Status changed from New to Affected

#3 Updated by Magoni Bruno almost 11 years ago

  • Assignee changed from Michaelis Renaud to Magoni Bruno

Xavier, as the workaround is fixed, do you agree to close this bug or should we move this demand to an evolution (for example setting this kind of configuration through the Web interface without having to change the scale's parameter) ?

#4 Updated by Mérour Xavier almost 11 years ago

OK, min and max scale have been defined.

I suggest to modify the configuration panel in order to prevent from this problem in a next release : for example, the root element should not be listed like the others but should clearly be put apart (different place ? in bold ?) or with an informative text to explain this configuration.
Better : set by default min and max scale to 0 for the root layer (like a global parameter...)!

To discuss...

#5 Updated by Mérour Xavier almost 11 years ago

Yes, Bruno, it can be move to an evolution for a next release.

#6 Updated by Magoni Bruno almost 11 years ago

  • Priority changed from Urgent to High

#7 Updated by Magoni Bruno almost 11 years ago

  • Assignee deleted (Magoni Bruno)

#8 Updated by Mérour Xavier almost 11 years ago

After some discussion... we still think that the "scale" workaround is a solution but the bug remain : the user should be able to load all layers of a service by choosing the root. BUT the user should just get the layers he has the right to see. Isn'it ?

The suggested "evolution" remain interesting... and might me done in a next release.

Thanks for your answer...

#9 Updated by Magoni Bruno almost 11 years ago

In WMS, a parent layer (ROOT or NOT) is able to display any map (one of her own or all the children layers); it depends on the configuration of the service.
So, it would be interesting to add through the PROXY the possibility to display the structure and/or the content of any parent layer.
This configuration should be made in the main config of the PROXY (default config) but also for each policy (specific config).
If the structure of a parent layer is visible but not his content (maps), the PROXY will use the workaround solution (min/max scale = 0).

#10 Updated by Magoni Bruno over 10 years ago

  • Target version set to 23

#11 Updated by Magoni Bruno about 10 years ago

  • Assignee set to Magoni Bruno

#12 Updated by Magoni Bruno about 10 years ago

  • Status changed from Affected to 5

#13 Updated by Magoni Bruno about 10 years ago

  • Status changed from 5 to New
  • Assignee deleted (Magoni Bruno)

#14 Updated by Magoni Bruno almost 10 years ago

  • Target version deleted (23)

#15 Updated by Mérour Xavier over 8 years ago

  • Target version set to Future

#16 Updated by Magoni Bruno over 5 years ago

  • Project changed from PROXY to easySDI
  • Target version deleted (Future)

#17 Updated by Magoni Bruno about 5 years ago

  • Assignee set to Mérour Xavier

Hi Xavier,

Is this ticket always relevant ?

Thanks,

#18 Updated by Mérour Xavier about 5 years ago

  • Assignee changed from Mérour Xavier to Magoni Bruno

I would keep this issue as a reminder (problem still exists) but change the priority to "low"

#19 Updated by Magoni Bruno about 5 years ago

  • Assignee deleted (Magoni Bruno)
  • Priority changed from High to Low

Also available in: Atom PDF