Fix api permissions

[kilichenko-pixida]

Aims to resolve
#12616 and #35

It seems like the problem was that permissions were assigned to None both when handling UI and API document upload. On UI it didn't cause a problem because in UI upload there is also a call setting permissions to defaults again.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @github-actions[bot] on file. In order for us to review and merge your code, please contact the project maintainers to get yourself added.

[gitguardian]

⚠️ GitGuardian has uncovered 26 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
59204	Triggered	Django Secret Key	deb7306	.env_local	View secret
59204	Triggered	Django Secret Key	7a448ec	.env.sample	View secret
59204	Triggered	Django Secret Key	deb7306	.env_dev	View secret
59204	Triggered	Django Secret Key	21373f9	.env.sample	View secret
59204	Triggered	Django Secret Key	deb7306	.devcontainer/.env	View secret
9705160	Triggered	Username Password	deb7306	geonode/base/api/tests.py	View secret
863333	Triggered	Generic Password	21373f9	.env_local	View secret
863333	Triggered	Generic Password	7a448ec	.env.sample	View secret
863333	Triggered	Generic Password	21373f9	.env_dev	View secret
863333	Triggered	Generic Password	21373f9	.env_test	View secret
863333	Triggered	Generic Password	7a448ec	.env_dev	View secret
863333	Triggered	Generic Password	21373f9	.env.sample	View secret
863333	Triggered	Generic Password	21373f9	.env_dev	View secret
863333	Triggered	Generic Password	7a448ec	.env_test	View secret
863333	Triggered	Generic Password	7a448ec	.env_local	View secret
863333	Triggered	Generic Password	21373f9	.env_local	View secret
863333	Triggered	Generic Password	7a448ec	.env_dev	View secret
863333	Triggered	Generic Password	7a448ec	.env_local	View secret
9468526	Triggered	Generic Password	21373f9	.env_test	View secret
9468526	Triggered	Generic Password	21373f9	.env_dev	View secret
9468526	Triggered	Generic Password	7a448ec	.env_local	View secret
9468526	Triggered	Generic Password	21373f9	.env.sample	View secret
9468526	Triggered	Generic Password	7a448ec	.env.sample	View secret
9468526	Triggered	Generic Password	7a448ec	.env_test	View secret
9468526	Triggered	Generic Password	7a448ec	.env_dev	View secret
9468526	Triggered	Generic Password	21373f9	.env_local	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}