Skip to main content

JBoss EAP 5 - 加密JEAP 5 的 admin 還有JMX console 密碼

這也是應觀眾要求!
==========================================


到 $jboss_install_path/server/default/conf 下有個login-config.xml 的檔案。
用搜尋找關鍵字jmx-console
把你想要的演算法跟編碼格式加入即可!

 <!-- A template configuration for the jmx-console web application. This defaults to the UsersRolesLoginModule the same as other and should be changed to a stronger authentication mechanism as required. --> 

<application-policy name="jmx-console"> 
  <authentication> 
  <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"> 
    <module-option name="usersProperties">props/jmx-console-users.properties</module-option> 
    <module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
    <module-option name="hashAlgorithm">MD5</module-option> <!-- 指定編碼的演算法 -->
    <module-option name="hashEncoding">base64</module-option> <!-- 指定編碼的格式 -->
  </login-module> 
  </authentication> 
 </application-policy>


再修改$jboss_install_path/server/default/conf/props/jmx-console-users.properties 中的密碼,改為加密後的版本即可!

# A sample users.properties file for use with the UsersRolesLoginModule
admin=NcgNLOKDvLQk0D+4/05RRA==

======================================================
 如何使用openssl產出編碼後的密碼,
======================================================
            
Linux:
   echo -n 1234 | openssl dgst -md5 -binary | openssl base64
Winodows: (Window 須先安裝openssl)
   <nul set /p "=1234" | openssl dgst -md5 -binary | openssl base64



Comments

Popular posts from this blog

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …