From ebf637221b4429dc89b5d6f3feb62c004009ee4e Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:41:37 +0000
Subject: [PATCH] Update wiki Home page for openstack-keystone

---
 Home.md | 43 +++++++++++++++++++++++++++++--------------
 1 file changed, 29 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..4d11b70 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,36 @@
-# Deploy the Project on CamelX Platform
+# OpenStack Keystone
 
-Deploy on CamelX Platform in three steps
+Access OpenStack Keystone for API client authentication, service discovery and distributed multi-tenant authorization.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `openstack-keystone` |
+| Support Level | Stable |
+| Labels | container |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-openstack</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `host` | string | ✓ |  | OpenStack host url |
+| `config` | object |  |  | OpenStack configuration |
+| `domain` | string |  | `default` | Authentication domain |
+| `operation` | string |  |  | The operation to do |
+| `password` | string | ✓ |  | OpenStack password |
+| `project` | string | ✓ |  | The project ID |
+| `subsystem` | string | ✓ |  | OpenStack Keystone subsystem |
+| `username` | string | ✓ |  | OpenStack username |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |