Display recovery token data in audit log #287
Merged
Conversation
This file contains 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
On the search pane, we now show audit log buttons for each RT entry. These link to the SF audit log page (but with a route of its own). Next up is to show the RT items in the audit log.
The translations/translations.twig file was created in a previous PR, it however is is a duplicate of the src/Surfnet/StepupRa/RaBundle/Resources/views/translations.html.twig All translations are now moved to the existing file
This data was not yet presented. It required the addition of two new columns for the recovery token identifier (eg phone number) and the RT type.
Base automatically changed from
feature/sat-revoke-token
to
feature/sat-recovery-tokens
July 19, 2022 11:16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This data was not yet presented. It required the addition of two new columns for the recovery token identifier (e.g. phone number) and the RT type.