LG-16022 Create daily ssa accounts report capability

[kevinsmaster5]

🎫 Ticket

LG-16022

🛠 Summary of changes

Adds a manually-run Rake report that generates a CSV and outputs a comma separated list of accounts that have logged in "yesterday", and share the same ssn_signature (assumed in part to mean they have the same ssn)

📜 Testing Plan

Provide a checklist of steps to confirm the changes.

• Create at least 2 idv test accounts in your local environment. When those are set up add their identity verification using the same mock SSN.
• Open the rails console and pick one of those test accounts. Update its last_authenticated_at value to Date.yesterday.middle_of_day

userfoo.identities.last.update(last_authenticated_at: Date.yesterday.middle_of_day)
userfoo.save

• Take note of the service_provider string on the profile and exit the console
• run the rake task: rake "duplicate_accounts:report["urn:gov:gsa:openidconnect:sp:sinatra"]"
• Expect an output to the terminal and a CSV be created in the <site_root>/tmp/duplicate_accounts directory

👀 Screenshots

[vrajmohan]

Made some comments.

[vrajmohan]

This was missed out in the original story - we only need active profiles.

[kevinsmaster5]

added active: true f2ac0cc

[vrajmohan]

Shouldn't this be i.last_authenticated_at?

[kevinsmaster5]

I had left i.last_authenticated_at in the WHERE filter and am grabbing u.updated_at thinking that's more closely tied to latest_activity_at in the story description. I can change that to last_authenticated if you think that's more to the point.

[vrajmohan]

The user could have authenticated to some other service provider, besides the service provider of interest. Wouldn't that mess with the updated_at?

[kevinsmaster5]

I'm not sure what the effect would be. I have modified the query to use i.last_authenticated_at with c8cf502

[vrajmohan]

Looks good.