automatically fill "baseUrl"; allow custom "username" in Auth resource #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
baseUrl
is filled automatically the first time the ExApp is installed. If it is not correct (e.g., due to differing network settings in the infrastructure), the Admin should adjust it. However, it works as expected in AIO and default Nextcloud installations.username
field is set toflow_app
by default, as it was before, but it can now be redefined. Our documentation does not currently explain its purpose or proper use. (My assumption: it might serve as the default user in Nextcloud for actions requiring a user but without one explicitly assigned, such as for a system flow user)A PR to the Nextcloud Docs with an update regarding
baseUrl
will be opened and linked to this one later.Resolves: #26