- Enhance the logging messages
- Minor enhancements

- Replace the logging services
- Move services to core plugin
  - CacheAPIUserAllowRunAs
  - ManageHosts
  - ServerAPIClient (aka api-interceptor)
  - ServerAPIHostEntries (aka )
  - UpdateConfigurationFile
  - UpdateRegistry
- Adapt the usage of services in the main and check updates plugin from
  core plugin
- Remove plugin logger from main and core plugins
- Remove API endpoint
  - GET /utils/logs/ui
- Remove unused code
- Adapt the test suites

…to enhancement/6137-adapt-logging-method

… yarn.lock files

…to enhancement/6137-adapt-logging-method

- Remove GET /utils/logs endpoint
  - Remove related tests
- Remove App logs application

- Create Configuration service
- Create ConfigurationStore (backend and frontend side)
- Register the plugin settings in the configuration services

…ration service

- API endpoints:
  - GET /utils/configuration
  - PUT /utils/configuration
  - PUT /utils/configuration/files/{key}
  - DELETE /utils/configuration/files/{key}

…on service

… service

…ttings

application

- Create API endpoints to manage the API host entries
  - PUT /hosts/apis/{id}
  - DELETE /hosts/apis/{id}
- Replace the Add new button on Server APIs application. Now it opens a
  flyout with a form to add the new API host
- Add edit and delete buttons to the table in Server APIs application
- Remove the render of old AddAPI component through AngularJS
- Remove deprecated methods of AngularJS controller related to Server
  APIs application
- Extend the definition of routes of main plugin to accept and use the
  configuration to validate the related endpoints

…inition

- Rename the `persistence` field to `store` in the settings definition
  to define how to store in the backend side
- Add readme files related to Configuration and ConfigurationStore
  services
- Add test for Configuration service
- Minor fixes in the Configuration service
- Define new methods for the Configuration instance of the frontend for
  the core plugin

…nition of main plugin

…on funtions

…y from configuration

- Refactor ManageHosts service:
  - Integrate the services within the ManageHosts service:
    - CacheAPIUserAllowRunAs
    - ServerAPIHostEntries
  - Renamed:
    - `serverAPIHostEntries.getHostsEntries` to `.getEntries`
    - `.getHostById` to `.get`
  - Adapted the usage of previous separated services
- Replaced the logic in the `DELETE /hosts/apis/{id}` by the usage of
  ManageHosts.delete instead of using the Configuration service
- Adapted the export types in the setup and start plugin life cycle
  methods
- Removed ServerAPIHostEntries: the methods were moved to ManageHosts
  service

- Remove getConfiguration service from the core and main plugins
- Replace partially the usage of getConfiguration service by
  Configuration
  - Add configuration dependency to the ReportPrinter and adapt when
    getting the configuration
  - Replace the usage on GET /api/logos
  - Replace some usages on the monitoring and statistics jobs
- Enhance the backend Configuration service with a .getCustomizationSetting method (replace the logic of old getCustomizationSetting)
- Remove the getCustomizationSetting service

- Enhance .getEntries method of ManageHost service
  - Adapt usage
- Enhance IConfiguration type

…en applying the configuration

- Close flyout of adding/editing API host entry when applying the
  configuration

…sionsOpenFlyout buttons

…I tables despite the current API is down

…nfiguration service

…to enhancement/6201-replace-plugins-configuration

- Remove deprecated services:
  - getCategorySettingByTitle
  - getSettingDefaultValue
  - getSettingsDefault
  - getSettingsByCategories
  - getSettingsDefaultList
  - groupSettingsByCategory
  - getPluginSettingDescription
  - services related to the creation of the initial file configuration

…ue to return

- Enhance ConfigurationStore services (frontend and backend side)
- Some replacements of the usage of configuration service

- Add Encryptation backend service
  - Create tests
  - Add new `wazuh_core.encryptation.password` plugin config to be used
    by this service
  - Create instance of this within the ConfigurationStore of the backend
    side
- Enhance the docs

- Add new DashboardSecurity service to frontend
  - Moved the logic of checkCurrentSecurityPlatform service to a method
    of the new service. Adapt its usage.
  - Replace the logic in the Server API table to use the new service to
    manage the button permissions
  - Create instance in the core plugin and expose to rest of plugins
- Move routeDecoratorProtectedAdministratorRoleValidToken to a new routeDecoratorProtectedAdministrator
  route decorator to protect the routes related to manage the configuration.
   - Affected endpoints:
     - PUT /hosts/apis/{id}
     - DELETE /hosts/apis/{id}
     - PUT /utils/configuration
     - PUT /utils/configuration/files/{key}
     - DELETE /utils/configuration/files/{key}
   - Adapted related tests
- Enhance types of public in core plugin
- Add new method isAdministrator to the security factories in the
  backend side

… Settings

- Rename Encryptation to Encryption service
- Moved the enhancement of Configuration service of the core plugin in
  the frontend side

- Create `user-manual` folder on `docs` of core plugin

- Move the API is down view
  - Remove render through AngularJS template
  - Remove properties defined in controller
  - Add a new callout to render in Server APIs
    - Include a button that opens a flyout with a basic troubleshooting

- Add a task to migrate the configuration file
> After the migration, the configuration file is renamed to avoid the future updates

- Rename setting property: isConfigurableFromFile to isConfigurableFromSettings
- Remove setting property: isConfigurableFromUI
- Remove the settingss definition on the main plugin and some types.
  Adapt the usage of types from the core plugin.

- Fix password fields on edition API host entry that
  displayed an error when this was not modified

- Create API endpoint: GET /utils/account/is-admin
- Refactor the DashboardSecurity method to get if the current user is
  an admin or not

…nistrator

…in setting

- Add add wazuh_core.security.administrator.roles plugin setting to
  define the administrator users

…ng settings on the server side

- Add endpoint to clear the configuration:
  POST /utils/configuration/clear
- Clear the configuration in the migration or script to set the
  configuration

…utils/account

…oint

- Rename properties of response of GET /utils/account
  - is_admin to administrator
  - message to administrator_message

- Support for multiple instances of configuration that gives the ability
  to deploy multiple instances of Wazuh dashboard with independant
  configurations

object stored

- Changes in the migrate configguration from file process:
  - Apply the migration process if there is no saved object stored yet.
  - Remove the renaming of file

…n the Reports application

…h_core.instance

…actions

- Change in Redux:
  - Create userAccount property in the appStateReducers
  - Create action creator for the userAccount property
- Fetch the userAccount data when the application is initiated
- Remove previous management of administrator actions
  - Remove Redux action creator
  - Remove state property
  - Remove hooks
  - Remove HOCs
- Remove constants from main and core plugins:
  - WAZUH_ROLE_ADMINISTRATOR_ID
  - WAZUH_ROLE_ADMINISTRATOR_NAME
- Replace the optional requirement of API roles by plugin administrator in the
  WzButtonPermissions
- Replace the optional requirement of API roles by plugin administrator in the
  authorization HOCs
- Replace the protection of endpoints to use the plugin administrator instead
  of based in API roles:
  - POST /elastic/samplealerts/{category}
  - DELETE /elastic/samplealerts/{category}

…o enhancement/6201-replace-plugins-configuration

…Value

…n_password to wazuh_core.configuration.encryption_key

…cess

- Replace the logic to consider the administrator user based on the rest
  API access
- Removed plugin setting: wazuh_core.security.administrator.roles
- Removed the required configuration of the DashboardSecurity service
  that is not necessary anymore

- Create CacheTTL class
- Add cache to ConfigurationStoreBackend

- Fix infinte loop of requests when there are not configured API hosts entries
- Fix update of API hosts entries when changin the index pattern

…o enhancement/6201-replace-plugins-configuration

…nstead

…OpenFlyout

…e component

- Create API endpoint to create API connections:
  - POST /hosts/apis/{id}
- Adapt the API request done by the form of API connection
- Adapt setup-configuration script to use the new API endpoint
- Add method to create API connection to the ManageHosts service

…agement

…iguration

- Create new API endpoint to import a configuration file
  - POST /utils/configuration/import
- Create method to enhance the configuration of the backend side to
  manage the importation
- Remove duplicated code to check if updating some settings requires to
  do some actions to apply

…o enhancement/6201-replace-plugins-configuration

… run the health check

…to wazuh-dashboard-plugins-config

… main plugin

…ries

- Remove API endpoint (route and controller)
- Remove API request of frontend side

…Hosts service

- Move the registry management to in memory cache managed by ManageHosts
  service.
  - Initialize the registry data on start
  - Update the registry on adding, editing or deleting an API host
- Remove the cacheAPIUserAllowRunAs of the ManageHosts service to use
  the registry data
  - Remove the cacheAPIUserAllowRunAs property of Manage hosts
- Move the logic to check if the run_as is enabled to the ManageHosts
  instead of cacheAPIUserAllowRunAs
- Remove the UpdateRegistry service
- Update the backend types of the core plugin

…o enhancement/6387-registry-stateless

…o enhancement/6387-registry-stateless

…com/wazuh/wazuh-kibana-app into enhancement/6387-registry-stateless

…g the id