Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How can an admin determine when someone's password last changed in Crowd?

Hi folks, how can I tell when someone last changed their password via Crowd?

I see User > Attributes > passwordLastChanged variable, but it's unclear how to convert this into a date. For example, what does this passwordLastChanged value signify?

1331653714613

4 answers

1 accepted

2 votes
Answer accepted

Solution: Remove the last three digits from Crowd's timestamps, then visit epochconverter.com in order to determine the date.

It seems that the dates in Crowd are too long to be standard Unix time because Crowd lists the dates as 13 digits, even though Unix time willl only be 10 digits long for the next ~7,992 years. According to Giuliano, the extra three digits represent milliseconds.

So if passwordLastChanged = 1331653714613 then ...


1. Truncate to only 10 digits: 1331653714

2. Enter this into epochconverter.com

3. Results:

GMT: Tue, 13 Mar 2012 15:48:34 GMT

Your time zone: Tue Mar 13 2012 11:48:34 GMT-4

1 vote
Giuliano C_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 17, 2012

Just to implement, you can convert this into a date through a third-party page:

http://www.onlineconversion.com/unix_time.htm

Kind Regards

Solution: remove the last three digits from Crowd's timestamps, then visit epochconverter.com in order to determine the date.

It seems that the dates in Crowd are too long to be standard Unix time because Crowd lists the dates as 13 digits, even though Unix time willl only be 10 digits long for the next ~7,992 years. According to Giuliano, the extra three digits represent milliseconds.

So if passwordLastChanged = 1331653714613 then ...

1. Truncate to 1331653714

2. Enter this into epochconverter.com

3. Results:

GMT: Tue, 13 Mar 2012 15:48:34 GMT

Your time zone: Tue Mar 13 2012 11:48:34 GMT-4

1 vote
Bhushan Nagaraj
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 16, 2012

Thank you Joe for informing us of this. I was starting to get a little crazy.

Without removing the last three digits I was getting things like:

Last Successful Login : 46522-12-20 22:26:55 -0700

Once I removed the last three difits all was good.
Last Successful Login : 2014-07-21 08:19:02 -0700
What confused me was that I was using the epochconverter.comwebsite to test the numbers I was working with and it was returning proper date/time. But in my Ruby code it was not. I guess the Ruby implementation does not account for ms.
In my User Class
@lastAuthenticated = (responseHash["attributes"][1]["values"][0])[0..-4].to_i

In my method where the output is displayed

puts "Last Successful Login : " + (Time.at(user.lastAuthenticated)).to_s

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events