You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the wonderful features in the UI, I'm seeking your feedback and thoughts on making UI Read-only. Specifically,
The feasibility of implementing a read-only UI or Something like running the UI container on a read-only mode
Role-Based Access Control:
Admin Users: Full access to all features and functionalities.
Read-Only Users: Limited access to view data without the ability to modify it.
The reason for asking this is, we have the app running on ECS with files and mappings mounted on EFS. We have a separate service that creates/modify the request mappings in the EFS and we use the UI to see matched/unmatched requests.
Thanks
Arul
The text was updated successfully, but these errors were encountered:
thx for this idea. I will look into it.
What you need to know though is that this wiremock fork uses the offical wiremock HTTP api. As far as I am aware this api does not know anything about rbac.
So this would be kind of a big feature. Furthermore, it would not be super secure and only rely on basic auth.
But I will think about this topic. It may take some time and I do not want to promise anything. I am having a full time job and all the open source stuff is something I need to do in my free-time.
Thanks for the wonderful features in the UI, I'm seeking your feedback and thoughts on making UI Read-only. Specifically,
The reason for asking this is, we have the app running on ECS with files and mappings mounted on EFS. We have a separate service that creates/modify the request mappings in the EFS and we use the UI to see matched/unmatched requests.
Thanks
Arul
The text was updated successfully, but these errors were encountered: