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
:rest-api-admin-replication--xref--put: {sgw--xref}{rest-api-admin--page}#/Replication/put__db___replication__replicationID_[Replication -- put model]
674
+
:rest-api-admin-replication--xref--put: {sgw--xref}{rest-api-admin--page}#tag/Replication/operation/put_db-_replication-replicationid[Replication -- put model]
Copy file name to clipboardExpand all lines: modules/ROOT/pages/_partials/sync-api/sync-function-api-expiry.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ This expiration time is not propagated when the document is replicated.
69
69
The purge of the document does not cause it to be deleted on any other database.
70
70
71
71
=== Inspect a Document Expiry Value
72
-
You can retrieve a document's expiration time, as it is returned in the response of GET xref:{rest-api--page}##/document/get__db___doc_[+/\{db/\{doc}] use `show_exp=true` as the querystring.
72
+
You can retrieve a document's expiration time, as it is returned in the response of GET xref:rest_api_public.adoc#tag/Document/operation/get_keyspace-docid[+/{keyspace}/{docid}+] using `show_exp=true` as the querystring.
For other providers we recommend to use Custom Authentication or OpenID Connect.
95
95
@@ -104,7 +104,7 @@ The last request creates a session.
104
104
105
105
image::custom-auth-flow.png[]
106
106
107
-
Given a user that has already been created, a new session for that user can be created on the Admin {rest-api-admin--pfx}#/session/post\__db___session[POST /+\{db}+/_session] endpoint.
107
+
Given a user that has already been created, a new session for that user can be created on the Admin xref:rest_api_admin.adoc#tag/Session/operation/post_db-_session[POST /+{db}+/_session] endpoint.
108
108
109
109
[source,bash]
110
110
----
@@ -124,7 +124,7 @@ The HTTP response body contains the credentials of the session.
124
124
* *name* corresponds to the `cookie_name`
125
125
* *value* corresponds to the `session_id`
126
126
* *path* is the hostname of the {sgw}
127
-
* *expirationDate* corresponds to the cookie's expiration time. The endpoint's {rest-api-admin--pfx}#/session/post\__db___session[API reference] contains more information about how the expiration time is automatically extended according to the user session activity.
127
+
* *expirationDate* corresponds to the cookie's expiration time. The endpoint's xref:rest_api_admin.adoc#tag/Session/operation/post_db-_session[API reference] contains more information about how the expiration time is automatically extended according to the user session activity.
128
128
* *secure* Whether the cookie should only be sent using a secure protocol (e.g. HTTPS)
129
129
* *httpOnly* Whether the cookie should only be used when transmitting HTTP, or HTTPS, requests thus restricting access from other, non-HTTP APIs
130
130
@@ -143,7 +143,7 @@ There are two implementation methods available with OpenID Connect:
143
143
144
144
<<implicit-flow>>::
145
145
With this method, the retrieval of the ID token takes place on the device.
146
-
You can then create a user session using the POST `+/\{tkn-db}/_session+` endpoint on the Public REST API with the ID token.
146
+
You can then create a user session using the POST `+/{db}/_session+` endpoint on the Public REST API with the ID token.
147
147
<<authorization-code-flow>>::
148
148
This method relies on {sgw} to retrieve the ID token.
149
149
@@ -166,32 +166,32 @@ In the algorithm dropdown, make sure to select `RS256` as the signing algorithm
166
166
. Upon successful validation, {sgw} authenticates the user based on the subject and issuer in the token.
167
167
168
168
Since Open ID tokens are typically large, the usual approach is to use the Open ID token to obtain a {sgw} session id (using the
Copy file name to clipboardExpand all lines: modules/ROOT/pages/changes-feed.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ For instance, if you have a channel called 'needs-email', you could have a bot t
41
41
== Endpoint
42
42
43
43
44
-
The changes feed API is a REST API endpoint (xref:rest-api.adoc#/database/get\__db___changes[`+/\{tkn-db}/_changes+`]) that returns a sorted list of changes made to documents in the database.
44
+
The changes feed API is a REST API endpoint (xref:rest_api_public.adoc#tag/Database-Management/operation/get_keyspace-_changes[`+/{keyspace}/_changes+`]) that returns a sorted list of changes made to documents in the database.
45
45
It permits applications to implement business logic that reacts to changes in documents.
0 commit comments