5 Commits (db1b244937e3356ed9ee977f17d0b21ef85e4ebe)

Author	SHA1	Message	Date
Kirill Solomko	1841d07d00	TT#172451 /api/passwordreset fix provisioning subscriber join ... * fix a join where webusername was fetched from the billing db instead of provisioning Change-Id: I1681c5fa1bac702d493168c2008d1ab911f910a6	3 years ago
Kirill Solomko	19547328d7	TT#172451 password reset uses webusername ... * the password reset via API now uses webusername instead of wrongly used username to fetch the subscriber Change-Id: Ib2ed042382963f13d73619acd48a588f3874c25b	3 years ago
Oleksandr Duts	752d81de48	TT#146103 API POST resetpassword - subscriber search fix ... * If user@domain is provided then looking for the specified domain, otherwise - url domain. Change-Id: I8ad9e0dab0f83eb8200d80e8ad993fba7c16abd3	3 years ago
Rene Krenn	eac6c2dc4c	TT#146101 add external base url parameter ... for deployments that expose panel/csc via a proxy, the auto-generated base url printed in emails can be unreachable. we therefore introduce the option to explicitly specify a base url to use. it will support an sprintf pattern with individual params for eg.: - protocol scheme - domain part - port - base url path Change-Id: I6a9ca23126c669d249ef7f3e092cae0161235ebe	3 years ago
Flaviu Mates	be14a9242e	TT#84337 - Implement /api/passwordreset ... * The new endpoint will only accept POSTs * The request body should have two parameters called 'type', 'username' and 'domain' * 'type' will accept either 'administrator', in which case only 'username' is needed, or 'subscriber', in which case 'username' and 'domain' will be needed * The regular password reset email will be sent to either the admin or the subscriber Change-Id: If1457c8c625a95295e5e93b6637927e3905698d9	5 years ago