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
{{ message }}
This repository was archived by the owner on Mar 11, 2022. It is now read-only.
initialization callback will always add the `cookieauth` plugin to the list of
285
284
configured plugins. If you do not want to use `cookieauth` then you should not
286
285
use this initialization callback, instead initalize the client without a
287
-
callback and then call the [ping function](https://cloud.ibm.com/docs/services/Cloudant/api?topic=cloudant-account#ping)
288
-
e.g.:
286
+
callback and then call the ping function e.g.:
289
287
290
288
```js
291
289
constc=newCloudant({
@@ -469,7 +467,7 @@ var cloudant = Cloudant({ url: myurl, maxAttempt: 5, plugins: [ { iamauth: { iam
469
467
(either because the IAM token service is down or the IAM API key is
470
468
incorrect) then an error is returned to the client.
471
469
472
-
See [IBM Cloud Identity and Access Management](https://cloud.ibm.com/docs/services/Cloudant/guides?topic=cloudant-ibm-cloud-identity-and-access-management-iam-) for more information.
470
+
See [IBM Cloud Identity and Access Management](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-account#authentication-iam) for more information.
473
471
474
472
You can turn off automatically refreshing token with the following configuration:
475
473
```js
@@ -555,7 +553,7 @@ This library adds documentation for the following:
555
553
556
554
Cloudant API keys are part of the legacy access controls. They are different from
557
555
the access control mechanisms offered by IBM Cloud IAM. See
0 commit comments