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
Copy file name to clipboardExpand all lines: modules/ROOT/pages/astream-faq.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,14 +100,14 @@ The following questions address security and access control in {product}.
100
100
101
101
=== Does {product} support single-sign on?
102
102
103
-
If your {product-short} organization is on a paid {product-short} subscription plan, your users can use SSO to sign in to the {astra-ui}.
103
+
If your {astra} organization is on a paid {astra} subscription plan, your users can use SSO to sign in to the {astra-ui}.
104
104
For more information, see xref:astra-db-serverless:administration:configure-sso.adoc[].
105
105
106
-
=== How do {product-short} roles and permissions map to {pulsar-short} roles and permissions?
106
+
=== How do {astra} roles and permissions map to {pulsar-short} roles and permissions?
107
107
108
108
See xref:ROOT:astream-org-permissions.adoc[].
109
109
110
-
=== What is the difference between {product-short} application tokens and the {pulsar-short} tokens?
110
+
=== What is the difference between {astra} application tokens and the {pulsar-short} tokens?
111
111
112
112
See xref:operations:astream-token-gen.adoc[].
113
113
@@ -128,7 +128,7 @@ See the following:
128
128
Unless you are starting a project from scratch, you likely have message data that needs to be brought over to your {product} tenants.
129
129
For migration assistance, contact {support-url}[IBM Support].
130
130
131
-
Every tenant in {product} comes with custom ports for Kafka and RabbitMQ workloads.
131
+
Every tenant in {product} comes with custom ports for {kafka-reg} and RabbitMQ workloads.
132
132
{company} also offers a fully-compatible JMS implementation for your Java workloads.
133
133
For more information, see xref:developing:starlight.adoc[].
134
134
@@ -161,7 +161,7 @@ Naturally, you have less control in a managed, serverless cluster than you do in
161
161
Beyond those differences, the effort to develop locally and then move to {product} should not be significant, but {company} recommends that you develop directly in {product}.
162
162
If you are trying to reduce costs, use the free tier of {product} and then switch when you are ready to stage your production services.
163
163
164
-
=== Can I use {product} with my existing Kafka or RabbitMQ applications?
164
+
=== Can I use {product} with my existing {kafka} or RabbitMQ applications?
Copy file name to clipboardExpand all lines: modules/ROOT/pages/astream-org-permissions.adoc
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
= Manage {product} roles and permissions
2
2
:navtitle: Manage roles and permissions
3
3
4
-
You manage role-based access control (RBAC) for {product} through your {product-short} organization.
5
-
For information about {product-short} RBAC, including default roles, custom roles, permissions, and user management, see xref:astra-db-serverless:administration:manage-database-access.adoc[].
4
+
You manage role-based access control (RBAC) for {product} through your {astra} organization.
5
+
For information about {astra} RBAC, including default roles, custom roles, permissions, and user management, see xref:astra-db-serverless:administration:manage-database-access.adoc[].
6
6
7
7
== {product} permissions
8
8
@@ -12,7 +12,7 @@ Permissions specific to {product} include the following:
12
12
13
13
=== Default roles for {product}
14
14
15
-
There are no default {product-short} roles specifically scoped to {product}.
15
+
There are no default {astra} roles specifically scoped to {product}.
16
16
However, the following default roles have the *Manage Streaming* permission:
17
17
18
18
* *Organization Administrator*
@@ -36,22 +36,22 @@ Additional permissions might be required, depending on the tasks the role needs
36
36
To control access to specific streaming tenants, you can set granular xref:astra-db-serverless:administration:manage-database-access.adoc#role-scopes[resource scopes] on custom roles.
37
37
====
38
38
39
-
== Authentication and authorization in {pulsar-reg} and {product-short}
39
+
== Authentication and authorization in {pulsar-reg} and {astra}
40
40
41
41
{pulsar-short} has the concept of https://pulsar.apache.org/docs/security-authorization/[clients with role tokens].
42
42
In {pulsar-short}, authentication is the process of verifying a provided token (JWT), and authorization is the process of determining if the role claimed in that token is allowed to complete the requested action.
43
43
44
44
{product} uses the {company} version of {pulsar} (xref:luna-streaming::index.adoc[Luna Streaming]).
45
45
The https://github.com/datastax/pulsar[Luna project] is an open fork of the {pulsar-short} project that maintains feature parity with OSS {pulsar-short}. {product}, as a managed service, abstracts some features/options of {pulsar-short} to ensure continuous, reliable service.
46
46
47
-
On a shared cluster, your {product-short} organization has one or more tenants on a shared {pulsar-short} cluster.
48
-
Each of your tenants is secured by {pulsar-short} authentication and authorization models, as well as your {product-short} organization's authentication and authorization ({product-short} RBAC).
47
+
On a shared cluster, your {astra} organization has one or more tenants on a shared {pulsar-short} cluster.
48
+
Each of your tenants is secured by {pulsar-short} authentication and authorization models, as well as your {astra} organization's authentication and authorization ({astra} RBAC).
49
49
50
50
{product} shared clusters are created and administered by {product} administrators.
51
51
Each tenant is assigned a custom role and permissions limited to that tenant only.
52
52
All tokens created within a tenant are assigned roles similar to the assigning tenant.
53
53
54
-
For programmatic access, you use {product-short} application tokens or {pulsar-short} JWT, depending on the operation you need to perform.
54
+
For programmatic access, you use {astra} application tokens or {pulsar-short} JWT, depending on the operation you need to perform.
55
55
For more information, see xref:operations:astream-token-gen.adoc[].
Copy file name to clipboardExpand all lines: modules/apis/pages/index.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
:description: Learn about the {product} {devops-api}.
3
3
4
4
The {product}{devops-api} is one of the APIs that you can use to manage your {pulsar-reg} tenants and their resources.
5
-
Use this API to manage higher-level {product} objects associated with your {product-short} organization, such as the Change Data Capture (CDC) settings, {pulsar-short} tenants, georeplication, {pulsar-short} stats, and {pulsar-short} tokens.
5
+
Use this API to manage higher-level {product} objects associated with your {astra} organization, such as the Change Data Capture (CDC) settings, {pulsar-short} tenants, georeplication, {pulsar-short} stats, and {pulsar-short} tokens.
6
6
7
7
.More endpoints
8
8
[TIP]
@@ -18,9 +18,9 @@ Other available APIs include the xref:apis:api-operations.adoc[{product} {pulsar
18
18
19
19
To use the {product}{devops-api}, you need the following:
20
20
21
-
* An active {product-short} account with access to {product}.
21
+
* An active {astra} account with access to {product}.
22
22
23
-
* An xref:operations:astream-token-gen.adoc[{product-short} application token] that has a role with {product} permissions.
23
+
* An xref:operations:astream-token-gen.adoc[{astra} application token] that has a role with {product} permissions.
24
24
25
25
* Depending on the operations you need to perform, you might need additional information about your tenant, such as the cluster name or {pulsar-short} instance name.
26
26
You can get this information with `<<get-tenant-details,GET "https://api.astra.datastax.com/v2/streaming/tenants">>` or from the xref:operations:create-delete-tenants.adoc#get-tenant-details[**Tenant Details** section in the {astra-ui}].
@@ -338,7 +338,7 @@ For more information, see xref:operations:astream-token-gen.adoc[].
338
338
339
339
[TIP]
340
340
====
341
-
For {product-short} application tokens, use the core xref:astra-db-serverless:api-reference:devops-api.adoc[{product-short} {devops-api}].
341
+
For {astra} application tokens, use the core xref:astra-db-serverless:api-reference:devops-api.adoc[{astra} {devops-api}].
0 commit comments