[0.12] Restrict user access using Accesspoints#583
[0.12] Restrict user access using Accesspoints#583v1r0x merged 41 commits intorelease-0.12-rebasedfrom
Conversation
Signed-off-by: Vinzenz Rosenkranz <vinzenz.rosenkranz@uni-tuebingen.de>
…feat-accesspoints
|
Please supply your test plugin that I can use for testing. |
|
Already uploaded 😉 |
| if(e.response.status == 401) { | ||
| systemStore.setAppState(true); | ||
| } else { | ||
| throwError(e); |
…#588) * Replaced manual file path with plugin methods * Added scope test plugin * Moved PluginScopes to a separate trait * Added cache to plugin scopes * Added test case for scopes
* Moved AccessPointLogic into a Service --------- Co-authored-by: Vinzenz Rosenkranz <vinzenz.rosenkranz@uni-tuebingen.de>
|
I would like you to document the accesspoint functionality in the docs (I already created the specific sections for it): Then I have no further objections to merge this. |
I started working on the texts, but it sure needs some polishing. |

Accesspoints allow admins to restrict access for users to certain parts of the application. Currently only a Default accesspoint is available, which redirects to the Spacialist main page. If no accesspoints are set for a user, the Default is used.
Plugins can extend the list of available accesspoints by defining them in their
info.xmlfile: