Support Questions

Find answers, ask questions, and share your expertise

How to reconnect to a new deployment

avatar
Explorer

 

Had issues with connecting to original deployment of Cloudera+Tableau Live, hence killed it.  When I add a new cluster via GoGrid portal, I can not connect to HUE or Cloudera Manager.  How to go about, if you kill your cluster?

1 ACCEPTED SOLUTION

avatar
Guru

The hashing algorithm has changed since then, but the general technique should work (and I thought it would migrate old hashes for existing passwords). I just tried this technique and it's working for me with newly generated hashes. This salt and hash should reset your 'admin' user's password to 'admin'. I would suggest you then immediately change it to something more secure since the port is open on a public network interface.

 

Salt: 7135628360540806339

Hash: 3a4e5ecfdf1a023e1302b7bef253de568357a995382702958517bbf238591101

View solution in original post

13 REPLIES 13

avatar
Guru

The hashing algorithm has changed since then, but the general technique should work (and I thought it would migrate old hashes for existing passwords). I just tried this technique and it's working for me with newly generated hashes. This salt and hash should reset your 'admin' user's password to 'admin'. I would suggest you then immediately change it to something more secure since the port is open on a public network interface.

 

Salt: 7135628360540806339

Hash: 3a4e5ecfdf1a023e1302b7bef253de568357a995382702958517bbf238591101

avatar
Explorer

Thank You Sean, I confirm the HASH & SALT for Cloudera Manager 5.3.x worked!  I will immediately change my password as you suggested.

 

I still think a CLI command or script is in order for the CDH5 framework.

avatar
Explorer

[ Correction ] The Cloudera Manager version in the ClouderaLive cluster as of today is:

 

Cloudera Enterprise Data Hub Edition Trial 5.1.0 (#75 built by jenkins on 20140716-1259)

avatar
Guru

>> I still think a CLI command or script is in order for the CDH5 framework.

 

I think that's a good idea - I'll file a feature request for this if one doesn't exist already. We'll also keep a look out for any reports of similar problems and look what might cause / be able to prevent it.

 

Thanks for the feedback!