-
Notifications
You must be signed in to change notification settings - Fork 9
Closed
Labels
BlockerWork can not proceed without this being resolvedWork can not proceed without this being resolvedUser StoryA user story as described by the clientA user story as described by the clientenhancementNew feature or requestNew feature or requestsoldThis issue was marked for execution in the current sprint. Applies to user storiesThis issue was marked for execution in the current sprint. Applies to user stories
Description
Is your feature request related to a problem? Please describe.
Authentication is the basis for all interaction with the telegram client. Understand the authentication mechanism present (are there refresh tokens, who issues API Keys, etc.)
Describe the solution you'd like
As we should have presentable things at the end of every sprint, and this probably will be the first thing to be requested, we should have a workable UI to simply login and logout, or directly logout if we have a cached authentication tokens.
Describe alternatives you've considered
No UI and simply authenticate via CLI. Worse, as they will expect a GUI at some point.
Additional context
See TDLIB authentication here in the docs.
Estimate:
3 Pizzen
Metadata
Metadata
Assignees
Labels
BlockerWork can not proceed without this being resolvedWork can not proceed without this being resolvedUser StoryA user story as described by the clientA user story as described by the clientenhancementNew feature or requestNew feature or requestsoldThis issue was marked for execution in the current sprint. Applies to user storiesThis issue was marked for execution in the current sprint. Applies to user stories