Skip to content
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.

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

[doc][ybm][faq] Add the reasoning behind not providing access to yugabyte user in YBM #21105

Closed
1 task done
mrajcevic01 opened this issue Feb 20, 2024 · 0 comments · Fixed by #23930
Closed
1 task done
Assignees
Labels
area/documentation Documentation needed

Comments

@mrajcevic01
Copy link
Contributor

Description

A common question many YBM users have is why do they not have access to the yugabyte user. This could be unexpected as they do have access to this user in open-source YugabyteDB. We do provide insight into this in a couple of places

When creating a cluster:

For security reasons, the database admin user does not have YSQL superuser privileges, but does have sufficient privileges for most tasks. For more information on database roles and privileges in YugabyteDB Managed, refer to Database authorization in YugabyteDB Managed clusters.

As well as in our Database Authorization section.

However this is met often enough to call this out in our FAQ for further visibility and for SEO purposes (if a user were to search for this)

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@mrajcevic01 mrajcevic01 added area/documentation Documentation needed status/awaiting-triage Issue awaiting triage labels Feb 20, 2024
@ddhodge ddhodge changed the title [Docs] Add the reasoning behind not providing access to yugabyte user in YBM [doc][ybm][faq] Add the reasoning behind not providing access to yugabyte user in YBM Sep 5, 2024
@ddhodge ddhodge self-assigned this Sep 5, 2024
ddhodge added a commit to ddhodge/yugabyte-db that referenced this issue Sep 15, 2024
ddhodge added a commit that referenced this issue Oct 2, 2024
…3930)

* Add reasoning behind no access to yugabyte user #21105

* Apply suggestions from code review

Co-authored-by: Aishwarya Chakravarthy  <[email protected]>

---------

Co-authored-by: Aishwarya Chakravarthy <[email protected]>
timothy-e pushed a commit that referenced this issue Oct 2, 2024
Summary:
 79a00fd [PLAT-15307]fix sensitive info leaks via Gflags
 cd26c93 [DOC-487] Voyager 1.8.2 changes (#24177)
 fa91de7 [docs] Apache Hudi integration with YSQL  (#23888)
 586d337 Updating DynamoDB comparison (#24216)
 aad5695 [#18822] YSQL: Promote autoflag to skip redundant update operations
 fa38152 Fix UBI image: Add -y option to install of hostname
 6baf188 [#23998] Update third-party dependencies and enable SimSIMD in Usearch
 d57db29 Automatic commit by thirdparty_tool: update usearch to commit 191d9bb46fe5e2a44d1505ce7563ed51c7e55868.
 aab1a8b Automatic commit by thirdparty_tool: update simsimd to tag v5.4.3-yb-1.
 161c0c8 [PLAT-15279] Adding unix timestamp to the core dump
 17c45ff [#24217] YSQL: fill definition of a shell type requires catalog version increment
 037fac0 [DB-13062] yugabyted: added banner and get started component
 2eedabd [doc] Read replica connection load balancing support in JDBC Smart driver (#24006)
 62a6a32 [#21467, #24153] Docdb: Add Read sequences as of time - sequences support for clone part 2
 12de78e [PLAT-14954] added support for systemd-timesyncd
 4a07eb8 [#23988] YSQL: Skip a table for schema comparison if its schema does not change
 d3fd39f [doc][ybm] Add reasoning behind no access to yugabyte user #21105 (#23930)
 556ba8a [PLAT-15074] Install node agents on nodes for the marked universes for on-prem providers
 9beb6dc [#22710][#22707] yugabyted: Update voyager migrations list landing page. (#22834)
 6128137 [PLAT-15545] Simplify the frozen universe message for end user in YBA
 4e36b78 JDBC Driver version update to 42.3.5-yb-8 (#24241)
 254c979 [PLAT-15519]: Update xCluster sync to remove tables from YBA DB

Test Plan: Jenkins: rebase: pg15-cherrypicks

Reviewers: tfoucher, fizaa, telgersma

Differential Revision: https://phorge.dev.yugabyte.com/D38624
@ddhodge ddhodge removed the status/awaiting-triage Issue awaiting triage label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Documentation needed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants