Release version 1.0.0

Author: pawel-baran-se

.github/workflows/docker-build.yml

@@ -11,7 +11,7 @@ env:
   # github.repository as <account>/<repo>
   IMAGE_NAME: mnestix-proxy
   # Update the version manually
-  IMAGE_TAG_VERSION: 0.1.0
+  IMAGE_TAG_VERSION: 1.0.0
 
 jobs:
   run-tests:

compose.yml

@@ -6,7 +6,7 @@
 services:
   mnestix-proxy:
     container_name: mnestix-proxy
-    image: mnestix/mnestix-proxy:0.1.0
+    image: mnestix/mnestix-proxy:1.0.0
     ports:
       - '5065:5065'
     environment:

wiki/Getting-started-with-developing.md

@@ -6,7 +6,6 @@ Before you start developing with **mnestix-proxy**, ensure you have the followin
 
 - **.NET 8 SDK** (required for building and running the project)
 - **Git** (for version control)
-- **Visual Studio Code** or **JetBrains Rider** (recommended IDEs)
 - **Docker** (optional, for containerized development and testing)
 
 ## Project Structure

wiki/Proxy-Configuration-Settings.md

@@ -60,7 +60,7 @@ Defines backend destinations for each route:
 - **aasRepoCluster**: `http://localhost:8081/`
 - **submodelRepoCluster**: `http://localhost:8081/`
 - **discoveryCluster**: `http://localhost:8082/`
-- **influxCluster**: `http://20.224.163.243:8086`
+- **influxCluster**: `http://<your-domain>:<port>`
 
 ---
 

wiki/Security-Configuration.md

@@ -1,6 +1,6 @@
 # Security Configuration
 
-This document describes the available security configuration options for the mnestix-proxy project, focusing on integration with **Keycloak** and **Azure Active Directory**.
+This document describes the available security configuration options for the mnestix-proxy project, focusing on integration with **Keycloak** and **Azure Entra ID**.
 
 ## Keycloak
 
@@ -10,7 +10,7 @@ Keycloak is an open-source identity and access management solution. To enable Ke
   Update your `appsettings.json` with the following section:
   ```json
   "OpenId": {
-    "EnableOpenIdAuth": "false",
+    "EnableOpenIdAuth": "true",
     "Issuer": "https://<keycloak-server>/realms/<realm-name>",
     "ClientID": "<client-id>",
     "RequireHttpsMetadata": "false"
@@ -20,28 +20,28 @@ Keycloak is an open-source identity and access management solution. To enable Ke
   The proxy will validate JWT tokens issued by Keycloak. Ensure your clients obtain tokens from Keycloak and include them in the `Authorization: Bearer <token>` header.
 
 
-## Azure Active Directory
+## Azure Entra ID
 
-Azure AD provides cloud-based identity management. To enable Azure AD authentication:
+Azure Entra ID provides cloud-based identity management. To enable Azure Entra ID authentication:
 
 - **Configuration**:  
   Update your `appsettings.json` with the following section:
   ```json
   "AzureAd": {
-    "EnableAzureAdAuth": "false",
+    "EnableAzureAdAuth": "true",
     "Instance": "https://login.microsoftonline.com/",
     "ClientId": "<client-id>",
     "Domain": "<your-domain>", 
     "TenantId": "<tenant-id>"
   }
   ```
 - **Usage**:  
-  The proxy will validate JWT tokens issued by Azure AD. Clients must authenticate with Azure AD and include the token in the `Authorization` header.
+  The proxy will validate JWT tokens issued by Azure Entra ID. Clients must authenticate with Azure Entra ID and include the token in the `Authorization` header.
 
 
 ## Additional Notes
 
-- Both Keycloak and Azure AD configurations rely on the standard ASP.NET Core authentication middleware.
+- Both Keycloak and Azure Entra ID configurations rely on the standard ASP.NET Core authentication middleware.
 - Ensure the `Audience` matches your application's client ID.
 - For development, you may set `RequireHttpsMetadata` to `false`, but it is recommended to use `true` in production.