Skip to content

Commit 7e9d1e1

Browse files
committed
restart managegui in init.sh to reload Shibboleth SP metadata
After `docker compose down -v`, the Shibboleth metadata cache is gone. When containers restart, managegui's Shibboleth SP tries to fetch IdP metadata from EngineBlock before init.sh has run migrations, causing a 503 and a 10-minute retry delay that breaks Manage login. This change ensures a managegui restart after the Manage push so Shibboleth re-fetches the metadata while EngineBlock is fully initialized and ready.
1 parent 68cc3b2 commit 7e9d1e1

1 file changed

Lines changed: 10 additions & 0 deletions

File tree

core/scripts/init.sh

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,16 @@ printf "\n"
114114
echo -e "${ORANGE}Send a PUSH in Manage, which pushes the entities to EngineBlock and OIDCNG ${VINKJE}"
115115
docker compose exec managegui curl -q -s -k -u sysadmin:secret $manageurl/push >/dev/null
116116

117+
printf "\n"
118+
echo -e "${ORANGE}Restarting managegui to reload Shibboleth SP metadata${NOCOLOR}"
119+
docker compose restart managegui
120+
echo -ne "Waiting for managegui to be ready..."
121+
until docker compose exec managegui curl -s -o /dev/null -w '%{http_code}' http://localhost/ 2>/dev/null | grep -qE '^[^5]'; do
122+
echo -n "."
123+
sleep 1
124+
done
125+
echo -e " ${VINKJE}"
126+
117127
printf "\n"
118128
echo -e "${BLUE}Please add the following line to your /etc/hosts: ${VINKJE}"
119129
printf "\n"

0 commit comments

Comments
 (0)