Deprecate one time ticket (1) (#156) #853
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
ikedas
changed the title
ikedas
force-pushed
the
deprecate_one_time_ticket-1
branch
from
b1669b5
to
af84006
Compare
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 may fix (partly) #156: This deprecates some of one-time ticket feature.
get_pending_listaction in notification about created/renamed lists for listmaster.searchaction in notification about failed unsubscriber for list owner.modindexaction in notification about held messages for list moderator.Now actions above need authentication on web interface.
On the other hand:
family_signoffaction: Since this action has never been documented nor completely implemented, it will be removed.family_signoffis documented. It should be rewritten not to use one-time ticket.sso_login/confirmemailaction ditto.choosepasswdaction ditto.