Update getValueFromDecodedAssertion docs

en/identity-server/7.3.0/docs/references/conditional-auth/api-reference.md

@@ -42,7 +42,7 @@
     - [`session`](#session)
     - [`application`](#application)
     - [`userAgent`](#user-agent)
     - [`connectionMetadata`](#connectionmetadata)
     - [`authConfig`](#authconfig)
 
 ---
@@ -68,11 +68,11 @@
 
 - **Example**
 
     ```bash 
     onLoginRequest(context)
     ```
 
 
 ### Execute a step
 
 `executeStep()`
@@ -116,7 +116,7 @@
 });
 ```
 
 #### Parameters
 This section describes the **options** you can use to configure the `executeStep()` function, and the values you can use as **local authenticators** and **federated IdPs** in the function.
 
 - <b>Options</b>
@@ -192,26 +192,26 @@
       </tbody>
     </table>
 
 
     The **external identity providers** are represented by the `idp` parameter. The federated connection names are generated based on the name you assign to the connection at registration.
 
     !!! tip "Example"
         If you add a [federated google connection]({{base_path}}/guides/authentication/social-login/add-google-login/) with the name **bifrost google**, the value you can use in your authentication scripts is `bifrost_google`.
 
 #### Examples
 Shown below are ways to define a login flow using the core functions.
 
 - <b>Example 1: Use <code>stepId</code></b>
 
     This example uses only the `stepId`.
     ``` js 
     executeStep(1)
     ```
 
 - <b>Example 2: Use <code>stepId</code> and <code>eventCallbacks</code></b>
 
     This example uses only the `stepId` and `eventCallbacks`.
     ``` js
     executeStep(1, {
         onSuccess: function(context) {
             //Do something on success
@@ -221,7 +221,7 @@
 
 - <b>Example 3: Use all parameters</b>
 
     This example uses the `stepId`, `options`, and an empty `eventCallbacks` object. Different properties can be 
     defined by the `options` object, such as `authenticationOptions`, `authenticatorParams` and `stepOptions`. However, you cannot write a script with only the `stepId` and `options`. 
 
     See the following examples:
@@ -738,6 +738,9 @@
     var state = getValueFromDecodedAssertion(context.request.params.request[0],"state",true);
     ```
 
+!!! note
+    This function only decodes the JWT — it does not verify the signature, issuer, audience, or expiry.
+
 ### Get unique user
 
 `getUniqueUserWithClaimValues(claimMap, context)`

en/identity-server/next/docs/references/conditional-auth/api-reference.md

@@ -738,6 +738,9 @@ This function returns a string containing the parameter's value in a decoded Jso
     var state = getValueFromDecodedAssertion(context.request.params.request[0],"state",true);
     ```
 
+!!! note
+    This function only decodes the JWT — it does not verify the signature, issuer, audience, or expiry.
+
 ### Get unique user
 
 `getUniqueUserWithClaimValues(claimMap, context)`

en/includes/references/conditional-auth/api-reference.md

@@ -793,6 +793,9 @@ This function returns a string containing the parameter's value in a decoded Jso
     var state = getValueFromDecodedAssertion(context.request.params.request[0],"state",true);
     ```
 
+!!! note
+    This function only decodes the JWT - it does not verify the signature, issuer, audience, or expiry.
+
 ### Get unique user
 
 `getUniqueUserWithClaimValues(claimMap, context)`