Project

General

Profile

Feature #5316

Avatar?id=6023&size=50x50 Avatar?id=6023&size=22x22

Account registration confirmation with email - HTTP API component support

Added by Artur Hefczyc TigaseTeam almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
High
Start date:
Due date:
% Done:

100%

Estimated time:
6.00 h
Source Code Disclaimer:

Description

The HTTP API component needs to accept an HTTP call with token in the URI to activate user account in pending status.

More details in the #5315

Please coordinate the work with Bartosz who works on the Tigase XMPP Server side support for this.

Before starting the work, provide approximate work estimation.

Associated revisions

Revision accb0526 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

#5316: replaced MailConfirmationTokenSender interface with more generic AccountValidator

Revision d9899a8c (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

#5316: added handler allowing account confirmation using token

History

#2 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

  • Estimated time set to 6.00 h

#3 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

  • Status changed from New to In QA
  • Assignee changed from Andrzej Wójcik to Artur Hefczyc

This is done.

I had to modify implementation created for account confirmation done by %bmalkow . Here is a list of changes:

  • enabling feature requires activation of bean account-registration-email-validator in root context:
'account-registration-email-validator'() {}
  • there is no longer need to enable it at JabberIqRegister processor level

  • confirmation web page provided by HTTP API will be enabled when mentioned bean is activated

#4 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

  • % Done changed from 0 to 100

#5 Avatar?id=6023&size=24x24 Updated by Artur Hefczyc TigaseTeam almost 2 years ago

  • Status changed from In QA to Closed

Also available in: Atom PDF