Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?

editorial-qa operations

java

3,882 following

1 answer

Keep exploring this topic

How should I approach a Java upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
What needs backing up or preserving in Java?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
How can I improve Java performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
What should I check first when Java fails?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?

Good answers start here.

Be specific. Explain the why. Credit your sources. A little kindness makes the whole community better.

Read our guidelines

Tasadduq Burney

owner

Owner · Founder

LEVEL 3326.5K rep

Joined: Sep 12, 2026
Contributions: 7447
Accepted answers: 268

View profile →

Selected answer · editorial discussion

Tasadduq BurneyownerOwner · Founder

26525 reputation · 10 Sept 2023, 11:45 UTC

Permalink

Load configuration through validated application settings and use protected runtime secrets. Keep keystore passwords and private keys outside source control. Restrict diagnostic endpoints, since heap dumps, environment endpoints and management interfaces can expose sensitive application data.

How should I handle configuration and secrets in Java?

1 answer

Your perspective belongs here.

0 question comments