Skip to content

Nextcloud - Clarifying the needed admin privileges#12886

Closed
tiagofreire-pt wants to merge 1 commit into
home-assistant:currentfrom
tiagofreire-pt:patch-2
Closed

Nextcloud - Clarifying the needed admin privileges#12886
tiagofreire-pt wants to merge 1 commit into
home-assistant:currentfrom
tiagofreire-pt:patch-2

Conversation

@tiagofreire-pt
Copy link
Copy Markdown
Contributor

Proposed change

Proposing a better text to clarify the needed admin privileges from the account on where the App pass is generated.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

@probot-home-assistant probot-home-assistant Bot added the current This PR goes into the current branch label Apr 12, 2020
@tiagofreire-pt tiagofreire-pt changed the title Clarifying the needed admin privileges Nextcloud - Clarifying the needed admin privileges Apr 12, 2020
This integration requires access to the monitor API of a Nextcloud instance Therefore, the account on where you should generate an App password from the Nextcloud web UI, must have `Administrator` privileges.

You should also generate an App password from the Nextcloud web UI: **Settings** > **Security** > **Devices & sessions** > **Create new app password**.
To create the needed App password follow this path on your Nextcloud instance: **Settings** > **Security** > **Devices & sessions** > **Create new app password**.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This 'App password' isn't actually required. You could use the admin's normal password, but that wouldn't be best practice.

## Configuration

This integration requires access to the monitor API of a Nextcloud instance (This is generally an admin user).
This integration requires access to the monitor API of a Nextcloud instance Therefore, the account on where you should generate an App password from the Nextcloud web UI, must have `Administrator` privileges.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The account doesn't necessarily need to be an admin user for this to work, the account would just need access to the monitor api - which i believe could be a non-admin user with additional monitor permissions. (don't ask me how to give a non-admin user those permissions though because I haven't tried it!)

Copy link
Copy Markdown
Contributor

@meichthys meichthys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggested changes, but i'm not sure they would be accurate. It is possible to:

  • use a normal password (not recommended)
  • use a non-admin user (would require some nextcloud server modifications, but would be possible and may be desired by some advanced users)

@meichthys
Copy link
Copy Markdown
Contributor

@tiagofreire-pt I will be submitting a pull request in the next day or so that should clarify these items.
Could you close this PR for now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

current This PR goes into the current branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants