Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add new type of
OskariComponent
calledLayerAccessHandler
to handle layer access.Currently the only method in the API
void handle(OskariLayer layer, User user);
gets called when a layer is "accessed" meaning when a data accessing request is made to the backing service via oskari-server. Right now this includes action routesGetLayerTile
for WMTS/WMS layers,GetWFSFeatures
for WFS/OAPIF layers, andGetPrint
for all types of layers asservice-print
works a bit differently. There's no way for this method to change the logic (except by throwing RuntimeExceptions I guess). LayerAccessHandler isn't meant for checking or validating anything but more for logging or monitoring purposes.The idea is to allow
server-extension
s to provide their own implementations ofLayerAccessHandler
s which will get loaded at runtime. For more discussion see: oskariorg/oskari-docs#243