Commit 71da38d6 authored by Kati Paizee's avatar Kati Paizee Committed by Shuang Zhang

Apply the suggestions for security part

parent d997dd71
...@@ -40,10 +40,11 @@ After the Harbor integration is activated: ...@@ -40,10 +40,11 @@ After the Harbor integration is activated:
- The global variables `$HARBOR_USER`, `$HARBOR_PASSWORD`, `$HARBOR_URL`, and `$HARBOR_PROJECT` are created for CI/CD use. - The global variables `$HARBOR_USER`, `$HARBOR_PASSWORD`, `$HARBOR_URL`, and `$HARBOR_PROJECT` are created for CI/CD use.
- The project-level integration settings override the group-level integration settings. - The project-level integration settings override the group-level integration settings.
## Best practice for security ## Secure your requests to the Harbor APIs
With every API request through Harbor integration, the credentials for your connection to Harbor API uses `username:password` combination, there are some suggestions for safe use: For each API request through the Harbor integration, the credentials for your connection to the Harbor API use
the `username:password` combination. The following are suggestions for safe use:
- Use TLS on the Harbor APIs you would connect to. - Use TLS on the Harbor APIs you connect to.
- Follow principle of least privilege (with respect to access on Harbor) with your credentials. - Follow the principle of least privilege (for access on Harbor) with your credentials.
- Have a rotation policy on your credentials. - Have a rotation policy on your credentials.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment