JanssenProject / JanssenProject/jans
fix(cloud-native): use custom properties to allow full control of ssl connection to persistence
Open
Nobody has claimed this yet.
kind-bug
- Dominant language
- Java
- Stars
- 648
- Forks
- 174
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 110
Description
Use custom `jans-pgsql.properties` and `jans-mysql.properties` to allow more control on ssl connection.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how jans-pgsql.properties and jans-mysql.properties are loaded and how persistence SSL settings are applied. Trace the database connection configuration for both PostgreSQL and MySQL, then verify that the custom properties provide full control of the SSL connection options for each backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql, postgresql
- Domain
- databases, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100