Skip to content
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.

Improve configured TomEE realms #60

Open
StavrevaS opened this issue Oct 25, 2017 · 2 comments
Open

Improve configured TomEE realms #60

StavrevaS opened this issue Oct 25, 2017 · 2 comments
Labels
P4 Priority 4 revisit

Comments

@StavrevaS
Copy link

In the current implementation, oscm realm and file-based tomee realm are active. The tomee admin must authenticate in both of them.

The file-based tomee realm should be initialized with with platform operator credentials in order to login to the tomee admin UI.

The platform operator will change his initial password. So there are 2 possibilities:

  • expose the users file to persistent store to be available for changes (needs probably restart of docker container - not good)
  • remove the file-based realm, keep only oscm realm. In case of failed oscm installation, the tommee admin GUI will also be unavailable.

The second option seems to be more convenient, since normally the operator should check the logs why an installation fails, the UI admin console is not really necessary,

@StavrevaS StavrevaS added this to the 17.6 milestone Oct 25, 2017
@shimizuf
Copy link

I favor the the second option. We should avoid config files outside of containers.

In case of failed oscm installation, the tommee admin GUI will also be unavailable
normally the operator should check the logs why an installation fails, the UI admin console is not really necessary
And if OSCM is not working, the whole TomEE is useless because we're in a specialized, contained environment.

@GoebelL GoebelL modified the milestones: 17.6, 18.0 Dec 15, 2017
@GoebelL GoebelL added the P4 Priority 4 label Mar 21, 2019
@GoebelL GoebelL removed this from the 18.0 milestone Jun 4, 2019
@GoebelL GoebelL added the revisit label Dec 9, 2020
@GoebelL
Copy link
Member

GoebelL commented Dec 9, 2020

The implemented solution was well suffient up to now. Nevertheless, let's revisit this issue once more.

I'm just thinking .... Would be nice for the operator, to have the option for enabling the TomEE admin GUI on-demand for use in non-productive environments. For instance, we had the need for executing MBeans that we deployed in an OSCM test environment. Sure there exists a solution for connecting both realms in OSCM. Due to lack of time for making the combined realms working, we chose another way for executing the MBeans. However, the services offered in the TomEE GUI could be helpful for many development, debugging and maintenance purposes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P4 Priority 4 revisit
Projects
None yet
Development

No branches or pull requests

4 participants