Repository navigation
feat(gateway): report TNT identity events to m1ngsama ID - #119
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TNT 1.8 tells the gateway about terminal sign-ins and key changes; this sends them to m1ngsama ID's activity log. Closes #117.
:loginreportstnt.signed_in;identity.recognized,identity.key_boundandidentity.signed_outbecometnt.key_recognized,tnt.key_boundandtnt.signed_outwith their fingerprint details.subonce and posts batches toPOST /internal/eventsastntwithTNT_GATEWAY_EVENTS_SECRET. Without the secret it reports nothing.$TNT_STATE_DIR/gateway-events.jsonand retried every 30 seconds, so a restart or an outage loses none. Events for a handle m1ngsama ID does not know are dropped and logged.Checked locally with TNT 1.8 and a local id Worker: :login twice, key binding, recognition and :logout appear in that order on /me/activity.