Return to Jive Software

Up to Discussions in Support
1,121 Views 4 Replies Last post: Feb 24, 2009 2:06 PM by Joe Travaglini RSS
Joe Travaglini Beginner
Joe Travaglini
578 posts since
Jan 10, 2008
Currently Being Moderated

Feb 12, 2009 12:40 PM

passwordHash, SaltSource, etc...

In the past I've been able to copy our database programatically to keep our QA environment in sync with production.

 

I haven't tested this out yet, but I am aware of the salt you guys have added to the password encoding.  Admittedly, I haven't dug into this too deeply.

 

What is this salt based on?  If I have a 3 node cluster in production as well as a 3 node cluster in QA that share a license, will they have the same salts?

 

I did a POC just trying to copy the passwordHash of a user from one DB to another, and could not log in on the app that points to the DB with the copied value.

 

Any help is appreciated.  Thanks

Tags: salt
Vinh Jive Employee
Vinh
12,343 posts since
Apr 1, 2008
Currently Being Moderated
Feb 12, 2009 1:08 PM in response to: Joe Travaglini
Re: passwordHash, SaltSource, etc...

Hey Joe,

 

It's salted by the creationDate. Copying the passwordHash and creationDate over should make the password correct.

 

Thanks,

Vinh

Joe Travaglini Beginner
Joe Travaglini
578 posts since
Jan 10, 2008
Currently Being Moderated
Feb 12, 2009 1:11 PM in response to: Vinh
Re: passwordHash, SaltSource, etc...

Nice, thanks Vinh

Vinh Jive Employee
Vinh
12,343 posts since
Apr 1, 2008
Currently Being Moderated
Feb 24, 2009 2:00 PM in response to: Joe Travaglini
Re: passwordHash, SaltSource, etc...

Hey Joe,

 

Can I make this case public?

 

Thanks,

Vinh

Joe Travaglini Beginner
Joe Travaglini
578 posts since
Jan 10, 2008
Currently Being Moderated
Feb 24, 2009 2:06 PM in response to: Vinh
Re: passwordHash, SaltSource, etc...

Sure, go for it.

More Like This

  • Retrieving data ...

Incoming Links

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.