Hi, if you are using the Geode1.1, Pulse uses the integrated security from your cluster now instead of having to resort to its own security. So the admin/admin username/password is only used when your cluster is not secured. If your cluster has a security manager, when logging into Pulse, you should use whatever username/password that can be authenticated by that security manager.
On Wed, Jun 28, 2017 at 1:27 AM, Dinesh Akhand <dines...@amdocs.com> wrote: > Hi team, > > > Is there any way to encrypted default username/password in > pulse.properties: > > # JMX User Properties > pulse.jmxUserName=admin > pulse.jmxUserPassword=admin > > spring-security.xml: > > <!-- Default user authentication --> > <beans:beans profile="pulse.authentication.default"> > <authentication-manager> > <authentication-provider> > <user-service> > <user name="admin" password="admin" > > authorities="ROLE_CLUSTER:READ,ROLE_DATA:READ"/> > </user-service> > </authentication-provider> > </authentication-manager> > I want to set default username/password to be in encrypted from in above > file. > Please suggest. > > Thanks, > Dinesh Akhand > > > -----Original Message----- > From: Dinesh Akhand > Sent: Tuesday, June 27, 2017 12:34 PM > To: dev@geode.apache.org > Subject: want to encrypt default username/password in properties files or > xml with default encrypted values. > > Hi Team, > > Default user name /password are defined in spring-security.xml and > pulse.properties file. > As below. > > ./geode/locator0/GemFire_anmuser/services/http/0.0.0.0_ > 20248_pulse/webapp/WEB-INF/spring-security.xml: > <user name="admin" password="admin" > ./geode/locator0/GemFire_anmuser/services/http/0.0.0.0_ > 20248_pulse/webapp/WEB-INF/classes/pulse.properties: > pulse.jmxUserPassword=admin > > What is the correct way to set the default encrypted username/password in > these config files. > > Please suggest. > > Thanks, > Dinesh Akhand > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > > you may review at https://www.amdocs.com/about/email-disclaimer < > https://www.amdocs.com/about/email-disclaimer> > > -- Cheers Jinmei
