As per specification:
In order to require additional information before changing the password, the server or service SHOULD return a Data Form in the error stanza:
Currently we just return error:
<!-- 2021-01-11T21:22:34Z >>>> --> <iq id='AD486CBD-3E70-4F60-AEC7-658E69742233' to='wojtek@tigase.org/585865504-tigase-22' type='set'> <query xmlns='jabber:iq:register'> <username>wojtek</username> <password></password> </query> </iq> <!-- 2021-01-11T21:22:34Z <<<< --> <iq type='error' xmlns='jabber:client' to='wojtek@tigase.org/585865504-tigase-22' from='wojtek@tigase.org/585865504-tigase-22' id='AD486CBD-3E70-4F60-AEC7-658E69742233'> <query xmlns='jabber:iq:register'> <username>wojtek</username> <password></password> </query> <error code='400' type='modify'> <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/> <text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>CAPTCHA is required. Please reload your registration form.</text> </error> </iq>
I think that for authenticated users we can just skip this requirement and just allow changing the password without additional requirements.
Seems to be fixed already (?!). Can't reproduce.
As per specification:
Currently we just return error:
I think that for authenticated users we can just skip this requirement and just allow changing the password without additional requirements.