diff --git a/bitnami/harbor-registry/2/debian-11/Dockerfile b/bitnami/harbor-registry/2/debian-11/Dockerfile
index 65bdd57cef02..64d3c081b565 100644
--- a/bitnami/harbor-registry/2/debian-11/Dockerfile
+++ b/bitnami/harbor-registry/2/debian-11/Dockerfile
@@ -3,10 +3,10 @@ FROM docker.io/bitnami/minideb:bullseye
 ARG TARGETARCH
 
 LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
-      org.opencontainers.image.created="2023-05-08T18:31:22Z" \
+      org.opencontainers.image.created="2023-05-11T13:59:29Z" \
       org.opencontainers.image.description="Application packaged by VMware, Inc" \
       org.opencontainers.image.licenses="Apache-2.0" \
-      org.opencontainers.image.ref.name="2.8.0-debian-11-r8" \
+      org.opencontainers.image.ref.name="2.8.0-debian-11-r9" \
       org.opencontainers.image.title="harbor-registry" \
       org.opencontainers.image.vendor="VMware, Inc." \
       org.opencontainers.image.version="2.8.0"
@@ -22,7 +22,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
 RUN install_packages ca-certificates curl procps
 RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
     COMPONENTS=( \
-      "harbor-registry-2.8.0-1-linux-${OS_ARCH}-debian-11" \
+      "harbor-registry-2.8.0-2-linux-${OS_ARCH}-debian-11" \
     ) && \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
diff --git a/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
index 099bcb6eddbe..7dbe7ba4ae4c 100644
--- a/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
+++ b/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
@@ -3,6 +3,6 @@
         "arch": "amd64",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "2.8.0-1"
+        "version": "2.8.0-2"
     }
 }
\ No newline at end of file
diff --git a/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/scripts/libos.sh b/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/scripts/libos.sh
index 02c989d693ae..6d9ca8546eef 100644
--- a/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/scripts/libos.sh
+++ b/bitnami/harbor-registry/2/debian-11/prebuildfs/opt/bitnami/scripts/libos.sh
@@ -421,7 +421,7 @@ generate_random_string() {
     alphanumeric+special|special+alphanumeric)
         # Limit variety of special characters, so there is a higher chance of containing more alphanumeric characters
         # Special characters are harder to write, and it could impact the overall UX if most passwords are too complex
-        filter='a-zA-Z0-9!@#$%^'
+        filter='a-zA-Z0-9:@.,/+!='
         ;;
     *)
         echo "Invalid type ${type}" >&2
diff --git a/bitnami/harbor-registry/README.md b/bitnami/harbor-registry/README.md
index 58e3b1827479..819647c0a89a 100644
--- a/bitnami/harbor-registry/README.md
+++ b/bitnami/harbor-registry/README.md
@@ -24,6 +24,8 @@ docker-compose up
 * All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading Linux distribution.
 * Bitnami container images are released on a regular basis with the latest distribution packages available.
 
+Looking to use Harbor Registry in production? Try [VMware Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
+
 ## How to deploy Harbor in Kubernetes?
 
 Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Harbor Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/harbor).