Skip to content

Security Rule Management Interface#516

Open
fpuhlig wants to merge 1 commit into
eclipse-basyx:mainfrom
fpuhlig:main
Open

Security Rule Management Interface#516
fpuhlig wants to merge 1 commit into
eclipse-basyx:mainfrom
fpuhlig:main

Conversation

@fpuhlig

@fpuhlig fpuhlig commented Jun 6, 2025

Copy link
Copy Markdown

Description of Changes

This pull request implements the following changes as part of the TINF23F SWE project:

  • Add Security Rule Management Interface
    • Implement a comprehensive security rule management UI with CRUD operations
    • Add filtering and search capabilities for security rules
    • Include detailed API call logging for debugging and monitoring
    • Implement role-based access control visualization
    • Add support for different target types (AAS, Submodel, Registry)
    • Include validation and error handling for all operations
    • Add tooltips and help text for better user guidance
    • Provide both mock and production versions of the security interface

Please see https://basyx-security-plugin.gitbook.io/basyx-security for a detailed documentation.

BaSyx Configuration for Testing

Testing has been performed with the following configuration:

  • Local development environment
  • Mock security submodel implementation

AAS Files Used for Testing

No actual AAS files were used for testing. Instead, we used mock data to simulate different security rule scenarios.

Additional Information

Developer: TINF23F Team 1
Main Repository of these changes: https://github.com/DHBW-TINF23F/Team1-BaSyx-Security-Plugin

Known Issues:

The production version (Security_PROD.vue) could not be fully tested due to a known bug in the BaSyx Java Server SDK that affects the RBAC container on macOS ARM architecture. (eclipse-basyx/basyx-java-server-sdk#707)

Security Considerations:

  • This implementation includes both a mock version (Security_MOCK.vue) for development and testing, and a production version (Security_PROD.vue) for actual deployment
  • All API endpoints and authentication mechanisms must be properly secured

@fpuhlig

fpuhlig commented Jun 6, 2025

Copy link
Copy Markdown
Author

@mrentsch65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant