Cloud Platform
Hide about this portal


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Feb 19, 2025

RELATED IDEAS

Allow JNDI as a mpConfig configuration source to allow encryption of secrets

See this idea on ideas.ibm.com

Currently, it is not clear whether any configuration source can benefit from the liberty encryption.
If this was possible, the secrets could be stored on disk in an encrypted way.

I know JNDI properties can be encrypted, so let's add JNDI to the existing ones:

  • 600 - server.xml -> appProperties -> property
  • 500 - server.xml -> variable
  • 400 - jvm.options
  • 300 - server.env
  • 100 - File META-INF/microprofile-config.properties
  • 1- server.xml -> variable with defaultValue

Source: https://openliberty.io/docs/latest/external-configuration.html

The idea is to add two things:

First idea

  • 550 - server.xml -> jndiEntry

e.g.:

<server>   <jndiEntry jndiName="schoolOfAthens/defaultAdminPassword" value="{aes}encryptedValue=" /> </server>

 

Then make it available via:

@Dependent class SomeService {  @Inject  @ConfigurationProperty( ... )  private  byte[] password; }

 

Example taken from: https://openliberty.io/docs/latest/reference/feature/jndi-1.0.html

second idea

Add a column to https://openliberty.io/docs/latest/external-configuration.html
whether values can be stored encrypted or not.

Describe why this is important to you:

Currently, the docs (https://openliberty.io/docs/latest/external-configuration.html) don't mention whether any of those can be stored encrypted (e.g. using securityUtility encode).

While this is not a sufficient encryption to stop hackers, it is better to not store passwords in plain text anyway.
The docs should also link to: https://openliberty.io/docs/latest/password-encryption.html

 

See: https://github.com/OpenLiberty/open-liberty/issues/27834 


 

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.