Skip to content

ENG-2540 Login record changes#3657

Merged
spwitt merged 4 commits intofeature/issue1from
spencer/eng-2540/login-record
Apr 18, 2025
Merged

ENG-2540 Login record changes#3657
spwitt merged 4 commits intofeature/issue1from
spencer/eng-2540/login-record

Conversation

@spwitt
Copy link
Contributor

@spwitt spwitt commented Apr 16, 2025

Document changes to login records that affect login record search and export APIs.

@spwitt spwitt requested review from a team as code owners April 16, 2025 20:50
@spwitt spwitt changed the title Spencer/eng 2540/login record ENG-2540 Login record changes Apr 16, 2025
@spwitt spwitt requested review from bhalsey and wied03 April 16, 2025 20:51
</APIField>
<APIField name="logins[x].loginId" type="String">
The email or username of the user. Because email or username may be modified after the login event occurred, only the <InlineField>userId</InlineField> and the should be considered immutable for historical purposes when identifying the user.
The identity used to log in. Because an identity may be modified after the login event occurred, only the <InlineField>userId</InlineField> should be considered immutable for historical purposes when identifying the user.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We now store the identity info in the raw_logins table when the login can be tied to a specific identity

  • If the identity info is stored with the login record, it will reflect the value used when the login occurred
  • If the login record does not have identity information, it will behave as before and look up the value from the database
  1. Is that acceptable behavior? I can’t think of a way around it.
  2. How far into the weeds do we want to go describing the behavior in docs?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good enough

@spwitt spwitt merged commit e3bbdc4 into feature/issue1 Apr 18, 2025
4 checks passed
@spwitt spwitt deleted the spencer/eng-2540/login-record branch April 18, 2025 18:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants