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
Copy file name to clipboardExpand all lines: docs/gateway-configuration/authentication-and-authorization.md
+32-33Lines changed: 32 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,76 +69,75 @@ Starting from Kura 5.5 the following restrictions will be applied by the Identit
69
69
70
70
## Temporary Identities
71
71
72
-
Kura 5.6 introduces the **TemporaryIdentityService**, a specialized service for creating and managing temporary, non-persistent identities. Temporary identities are designed for short-lived authentication scenarios where identity persistence is not required.
72
+
Kura 6 introduces temporary identity support in the **IdentityService**, a set of APIs for creating and managing temporary, non-persistent identities. Temporary identities are designed for short-lived authentication scenarios where identity persistence is not required.
73
73
74
74
### Key Characteristics
75
75
76
76
-**Non-Persistent**: Temporary identities exist only in memory and are never persisted to disk or configuration snapshots
77
-
-**Token-Based Authentication**: Each temporary identity is associated with a unique authentication token
77
+
-**Password-Based Authentication**: Each temporary identity uses a generated password for authentication
78
78
-**Automatic Lifecycle Management**: Temporary identities can be programmatically created and deleted as needed
79
79
-**Permission-Based Authorization**: Temporary identities support the same permission model as regular identities
80
-
-**No Password Management**: Temporary identities use token-based authentication and do not require password management
81
80
82
81
### Primary Use Case: Container Identity Integration
83
82
84
83
The main use case for temporary identities is the **Container Identity Integration** feature, which automatically provisions authentication credentials for containerized applications. When a container is configured with identity integration enabled:
85
84
86
85
1. Kura creates a temporary identity with the specified permissions
87
-
2. Generates a unique authentication token for the identity
88
-
3. Provides the token to the container via environment variables
86
+
2. Generates a temporary password for the identity
87
+
3. Provides the identity name and password to the container via environment variables
89
88
4. Automatically cleans up the temporary identity when the container stops
90
89
91
-
This allows containers to securely access Kura's REST APIs without manual credential configuration or exposing persistent credentials.
90
+
This allows containers to securely access Kura's REST APIs without manual credential configuration or exposing persistent credentials. Password-based REST authentication requires **Basic Authentication Enabled** in the **RestService** configuration.
92
91
93
-
### TemporaryIdentityService API
92
+
### Temporary Identity API
94
93
95
-
The `TemporaryIdentityService` provides the following operations:
94
+
Temporary identities are managed through the `IdentityService` APIs using an `IdentityConfiguration` and a lifetime:
-[Container Identity Integration](../core-services/container-orchestration-provider-usage.md#container-identity-integration) - Detailed guide on using temporary identities with containers
164
-
-[How to Use Temporary Identity Service](../java-application-development/how-to-use-temporary-identity-service.md) - Developer guide for using the TemporaryIdentityService API
163
+
-[How to Use Temporary Identities](../java-application-development/how-to-use-temporary-identity-service.md) - Developer guide for using IdentityService temporary identity APIs
0 commit comments