@adobe/acc-js-sdk 1.1.25 → 1.1.27

package/docs/changeLog.html

@@ -2,6 +2,29 @@
 layout: page
 title: Change Log
 ---
+
+<section class="changelog"><h1>Version 1.1.27</h1>
+  <h2>2023/05/10</h2>
+  <li>
+    Fixed a unit test which was failing in Node 16 but succeeding on node 14. The reason is that the error message thrown by Node when accessing a property of a null object changed between the 2 versions.
+  </li>
+  <li>
+    The `client.getSchema` and `application.getSchema` functions are now able to return group schemas 
+    (using the temp:group:{id} format for the schema id). See <a href="https://opensource.adobe.com/acc-js-sdk/xtkSchema.html"></a> for more information.
+  </li>
+</section>
+
+<section class="changelog"><h1>Version 1.1.26</h1>
+  <h2>2023/04/17</h2>
+
+  <li>
+    Added support for IMS Bearer tokens without require any session and security tokens. See <a href="https://opensource.adobe.com/acc-js-sdk/connecting.html"> for more details.</a>
+  </li>
+  <li>
+    Fixed a bug causing incorrect JSON to XML transformation when the JSON object has a property named 'length'
+  </li>
+</section>
+
 <section class="changelog"><h1>Version 1.1.25</h1>
   <h2>2023/03/07</h2>
 
@@ -15,7 +38,7 @@ title: Change Log
 </section>
 
 <section class="changelog"><h1>Version 1.1.24</h1>
-  <h2>2023/03/07</h2>
+  <h2>2023/04/07</h2>
 
   <li>
     Added support for abortable requests. See <a href="https://opensource.adobe.com/acc-js-sdk/abortRequest.html"> for more details.</a>

package/docs/connecting.html

@@ -51,19 +51,58 @@ await client.logoff();
     <li>Informations about the connected user, and it's privileges</li>
 </ul>
 
-<p>T
-    he most convenient way to access this information is by using the <a href="{{ site.baseurl }}/application.html">Application object</a>, but you can
+<p>The most convenient way to access this information is by using the <a href="{{ site.baseurl }}/application.html">Application object</a>, but you can
     also use the <b>client.getSessionInfo().serverInfo</b> and <b>client.getSessionInfo().sessionInfo</b> calls.
 </p>
 
+<p class="info">Note: depending on the type of credentials used, user and server info may not be returned.
+</p>
 
+<table>
+    <thead>
+        <tr>
+            <th>Credentials Type</th>
+            <th>Returns info</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>UserPassword</td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>ImsServiceToken</td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>SessionToken</td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>AnonymousUser</td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>SecurityToken</td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>BearerToken</td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>ImsBearerToken</td>
+            <td>No</td>
+        </tr>
+    </tbody>
+</table>
 
 <h1>Credentials</h1>
 
 <p>
     There are several methods of the <b>sdk.ConnectionParameters</b> depending on the type of authentication you want to use. They are
     described below.
-</p>>
+</p>
 
 <h2>Login with user and password</h2>
 <p>This is the most common method to log in to Campaign. User the <b>ofUserAndPassword</b> function and pass it the user name and password</p>
@@ -75,7 +114,26 @@ const connectionParameters = sdk.ConnectionParameters.ofUserAndPassword(
 
 
 <h2>Login with IMS access token</h2>
-<p>The SDK supports IMS access token of an IMS user with the <b>ofBearerToken</b> function. Pass it a bearer token.</p>
+
+<p>In Campaign 8.5 and above, native support for IMS bearer tokens is avaiable and can be used in the SDK as the preferred connection method.</p>
+<pre class="code">
+    const connectionParameters = sdk.ConnectionParameters.ofImsBearerToken(
+                                    "https://myInstance.campaign.adobe.com", 
+                                    "ims_bearer_token");
+</pre>
+
+
+<p class="info">Note: You still need to call Logon
+</p>
+
+<p>With this authentication method, an IMS Bearer token is obtained outside of Campaign, for example using IMS APIs and is passed directly to 
+    all Campaign APIs. Campaigns itslef will verify the token and grant the corresponding access.
+</p>
+
+    
+<p>For older versions of Campaign, you can still use IMS tokens with the <b>ofBearerToken</b> function. The difference between ofImsBearerToken and ofBearerToken
+    is that ofBearerToken will internally call "xtk:session#BearerTokenLogon" to exchange the IMS token for Campaign session and security tokens. Subsequent
+    API calls will use Campaign tokens. It's recommended to us <b>ofImsBearerToken</b> logon whenever possible.</p>
 <pre class="code">
 const connectionParameters = sdk.ConnectionParameters.ofBearerToken(
                                 "https://myInstance.campaign.adobe.com", 

package/docs/samples.html

@@ -3,7 +3,7 @@ layout: page
 title: Sample Code
 ---
 
-<p>The <b>samples</b> folder contains several samples illustrating how to use the various Campaing APIs.</p>
+<p>The <b>samples</b> folder contains several samples illustrating how to use the various Campaign APIs.</p>
 
 <p>A sample file looks like this</p>
 

package/docs/xtkSchema.html

@@ -36,4 +36,20 @@ var srcSchema = await NLWS.xtkPersist.getEntityIfMoreRecent("xtk:srcSchema|nms:r
 console.log(JSON.stringify(srcSchema));
 </pre>
 
-
+<h1>Group schemas</h1>
+
+<p>
+Campaign groups represent marketing lists or audiences. Each group can have it's own specific schema, 
+stored in the `extension` XML element of the group entity. This schema can be generated in a workflow by 
+using the List Update activity.
+</p>
+<p>
+The schema of a group can be retrieved using the `getSchema` method of the client or application objects.
+</p>
+<p>
+The schema id is build as followed: prefix `temp:group:` + id of the group in mms:group (example `temp:group:1234` )
+</p>
+
+<p>Note: group schemas are not cached. The rationale is that they are not accessed as frequently as other,
+  regular schemas, but more importantly that they can change more often that regular schemas.
+</p>