Skip to content

DOC-1629: Fix single sourcing and cross repo tags #1329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Aug 20, 2025
Merged

DOC-1629: Fix single sourcing and cross repo tags #1329

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
e6bac48
DOC-1629: Fix single sourcing and cross repo tags
Feediver1 Aug 20, 2025
52ae588
removed unsupported tag
Feediver1 Aug 20, 2025
b6d35a9
fix typo in xref
micheleRP Aug 20, 2025
8070993
DOC-1629: Fix single sourcing and cross repo tags
Feediver1 Aug 20, 2025
d4b23b5
removed unsupported tag
Feediver1 Aug 20, 2025
cfb5b2a
fix typo in xref
micheleRP Aug 20, 2025
acd9076
conditionalize out note for schema_id_validation
micheleRP Aug 20, 2025
f6bf811
Merge branch 'DOC-1629' of github.com:redpanda-data/docs into DOC-1629
micheleRP Aug 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions modules/manage/pages/schema-reg/schema-reg-authorization.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,14 +257,22 @@ User `jane` now has global `read` and `write` access to the Schema Registry and

=== Create a role with Schema Registry ACLs

ifdef::env-cloud[]
You can combine Schema Registry ACLs with xref:security:authorization/rbac/rbac_dp.adoc[role-based access control (RBAC)] to create reusable roles. This approach simplifies permission management when you need to assign the same set of permissions to multiple users.
endif::[]

ifndef::env-cloud[]
You can combine Schema Registry ACLs with xref:manage:security/authorization/rbac.adoc[role-based access control (RBAC)] to create reusable roles. This approach simplifies permission management when you need to assign the same set of permissions to multiple users.
endif::[]

This example creates a role called `SoftwareEng` and assigns it ACLs for both topic and Schema Registry access:

ifndef::env-cloud[]
[NOTE]
====
Redpanda recommends using the topic naming strategy for Schema Registry subjects, where subjects follow the pattern `<topicName>-key` or `<topicName>-value`. For details, see xref:manage:schema-reg/schema-id-validation.adoc#set-subject-name-strategy-per-topic[Set subject name strategy per topic].
====
endif::[]

[,bash]
----
Expand Down Expand Up @@ -344,6 +352,7 @@ User:alice * TOPIC bar LITERAL READ
The `Not found` error occurs in the request: `12:17:33.935 DEBUG sending request {"method": "POST", "URL: "http://127.0.0.1:8081/security/acls", "has_bearer": false,
"has_basic_auth": false}`, meaning that the endpoint is not available (because you are using an older Redpanda version). You must upgrade to the current version of Redpanda.

ifndef::env-cloud[]
This next error occurs when the user tries to create two ACLs, one for a topic and one for a registry-subject:

[bash]
Expand All @@ -364,6 +373,7 @@ User:mary * TOPIC private LITERAL READ
----

The `Invalid license: not present` error indicates that the user is trying to create an ACL for a resource that requires a license, but no license is present. See xref:get-started:licensing/overview.adoc[Licensing overview] for details on how to obtain a license.
endif::[]

== Suggested reading

Expand Down