Actions
Feature #2678
openAccess restriction for Discovery sites
Start date:
2025-11-15
Estimated time:
Description
We currently have a request to deploy an access restricted Discovery instance. Bernhard suggested that this could be a configurable feature.
My initial ideas depending on available resources and work needed:- Functionality to set a flag that credentials are needed and solve the authentication elsewhere
- Functionality to set a flag and the credentials in a secure way (e.g. not tracked via Git)
- Postpone this functionality (e.g. Wishlist) and solve the current request "manually"
Updated by Alexander Watzinger about 1 month ago
- Related to Feature #2677: New instance for Welterbe Salzkammergut added
Updated by Bernhard Koschiček-Krombholz about 1 month ago
- Related to Feature #2682: JWT Token added
Updated by Alexander Watzinger 29 days ago
- Status changed from New to Assigned
- Assignee set to Katharina Wünsche
- Target version set to 1.1.0
Updated by Katharina Wünsche 9 days ago
- Target version changed from 1.1.0 to Wishlist
We managed to add some simple authentication based on the NGINX Ingress Controller (see https://redmine.acdh.oeaw.ac.at/projects/dsie/wiki/Varia_-_Basic_authentication_over_NGINX_Ingress_Controller). More advanced authentication features might follow in the future.
Updated by Alexander Watzinger 9 days ago
- Status changed from Assigned to Acknowledged
- Assignee deleted (
Katharina Wünsche)
Actions