Skip to content

Disable HTTP_PORT and automatic config monitoring - #780

Open
kabicin wants to merge 23 commits into
vNextfrom
sec-enhancements
Open

Disable HTTP_PORT and automatic config monitoring#780
kabicin wants to merge 23 commits into
vNextfrom
sec-enhancements

Conversation

@kabicin

@kabicin kabicin commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator
  • Removes the HTTP_PORT config and allows setting environment variable ENABLE_HTTP_PORT to true to re-enable it in configure.sh
  • Disables automatic config updates by default
  • Runs productInfo validate after features are installed in features.sh

USER 1001

EXPOSE 9080 9443
EXPOSE 9443

@leochr leochr Aug 12, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The warm up as part of SCC generation relies on 9080. We should use HTTPS by default if the /openapi endpoint can still be invoked.

WARM_ENDPOINT_URL=localhost:9080/

@kabicin
kabicin marked this pull request as ready for review August 14, 2026 20:47

@leochr leochr left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kabicin Thanks for the PR. Added some comments. As discussed, we should enable these by default for UBI Micro only. We could use the same configure.sh between the UBI variants and set the flag to enable in the relevant Dockerfile only.

find /opt/ibm/wlp/lib /opt/ibm/wlp/bin ! -perm -g=rw -print0 | xargs -0 -r chmod g+rw

# Validate the Liberty installation integrity after feature installation
/opt/ibm/wlp/bin/productInfo validate

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a flag to skip validate. We should still validate by default.

<server>
<!-- Disable automatic configuration file monitoring.
The server will not reload config after startup; a restart is required to apply changes. -->
<config updateTrigger="disabled" />

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please run the Operator FVT tests with this turned on to ensure that the Operator functionalities, beside Trace, won't be impacted (in particular LTPA).

@@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change file name (i.e. update-trigger-disabled.xml)

mkdir -p ${SNIPPETS_TARGET_DEFAULTS}

# Disable automatic configuration file monitoring (security hardening)
cp $SNIPPETS_SOURCE/config-mbean.xml $SNIPPETS_TARGET/config-mbean.xml

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a flag to skip over disabling update trigger.

Should we write to the SNIPPETS_TARGET_DEFAULTS directory so admins/users can override in server.xml?

WARM_ENDPOINT_URL=https://localhost:9443/
WARM_OPENAPI_ENDPOINT=true
WARM_OPENAPI_ENDPOINT_URL=localhost:9080/openapi
WARM_OPENAPI_ENDPOINT_URL=https://localhost:9443/openapi

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validate that https://localhost:9443/openapi endpoint can still be invoked successfully (which should generate additional cache).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants