Merge pull request #96727 from eromanova97/manual-cp-95708-to-6.0

[standalone-logging-docs-6.0] OBSDOCS-2061: fix 'logging-identity-federation.adoc' and remove duplicate

Author: eromanova97

modules/identity-federation.adoc

@@ -4,19 +4,23 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="logging-identity-federation_{context}"]
-= Workload identity federation
-Workload identity federation enables authentication to cloud-based log stores using short-lived tokens.
+= Authenticating with workload identity federation to access cloud-based log stores
+
+You can use workload identity federation with short-lived tokens to authenticate to cloud-based log stores. With workload identity federation, you do not have to store long-lived credentials in your cluster, which reduces the risk of credential leaks and simplifies secret management.
 
 .Prerequisites
-* {ocp-product-title} 4.14 and later
-* {logging-uc} 5.9 and later
+
+* You have administrator permissions.
 
 .Procedure
-* If you use the {ocp-product-title} web console to install the {loki-op}, clusters that use short-lived tokens are automatically detected. You are prompted to create roles and supply the data required for the {loki-op} to create a `CredentialsRequest` object, which populates a secret.
 
-* If you use the {oc-first} to install the {loki-op}, you must manually create a subscription object using the appropriate template for your storage provider, as shown in the following examples. This authentication strategy is only supported for the storage providers indicated.
+* Use one of the following options to enable authentication:
 
-.Azure sample subscription
+** If you used the {ocp-product-title} web console to install the {loki-op}, the system automatically detects clusters that use short-lived tokens. You are prompted to create roles and supply the data required for the {loki-op} to create a `CredentialsRequest` object, which populates a secret.
+
+** If you used the {oc-first} to install the {loki-op}, you must manually create a `Subscription` object. Use the appropriate template for your storage provider, as shown in the following samples. This authentication strategy supports only the storage providers indicated within the samples.
++
+.{azure-first} sample subscription
 [source,yaml]
 ----
 apiVersion: operators.coreos.com/v1alpha1
@@ -25,7 +29,7 @@ metadata:
   name: loki-operator
   namespace: openshift-operators-redhat
 spec:
-  channel: "stable-5.9"
+  channel: "stable-6.0"
   installPlanApproval: Manual
   name: loki-operator
   source: redhat-operators
@@ -41,8 +45,8 @@ spec:
       - name: REGION
         value: <your_region>
 ----
-
-.AWS sample subscription
++
+.{aws-first} sample subscription
 [source,yaml]
 ----
 apiVersion: operators.coreos.com/v1alpha1
@@ -51,7 +55,7 @@ metadata:
   name: loki-operator
   namespace: openshift-operators-redhat
 spec:
-  channel: "stable-5.9"
+  channel: "stable-6.0"
   installPlanApproval: Manual
   name: loki-operator
   source: redhat-operators