Description
When use a authkey with integration of MapStore and GeoServer, OGC services return the authkey in the URLs of Capabilities or Catalogs. They have to be removed before to add the layer to the system to avoid duplicated auth-keys.
Browser Affected
any
Steps to reproduce
- Login to a MapStore instance integrated with GeoServer
- Create a dashboard with a widget connected to a layer (chart, table...) You will see the authkey parameters will be saved in teh
- Open the developer tools and save the dashboard.
Expected Result
- No auth data is saved in the resource
- The widget will work even when your session has expired.
Current Result
You will see the widget's layer object in the JSON posted contains ms2-authkey parameter in the URL.
If you logout and open mapstore when session is expired (e.g. the day after), the widget may have some errors due to authentication.
Description
When use a authkey with integration of MapStore and GeoServer, OGC services return the authkey in the URLs of Capabilities or Catalogs. They have to be removed before to add the layer to the system to avoid duplicated auth-keys.
Browser Affected
any
Steps to reproduce
Expected Result
Current Result
You will see the widget's layer object in the JSON posted contains ms2-authkey parameter in the URL.
If you logout and open mapstore when session is expired (e.g. the day after), the widget may have some errors due to authentication.