nextcloud

目錄樹: a733a77f7b

作者	SHA1	備註	提交日期
Carl Schwan	3fa6ee3c60	Fix login flow Signed-off-by: Carl Schwan <carl@carlschwan.eu>	1 年之前
Lukas Döllerer	1a817453a2	Add button disable on submit for login grant Signed-off-by: Lukas Döllerer <info@lukas-doellerer.de>	2 年之前
Daniel Kesselberg	71c7442790	The loading animation is back Refactor grant.js to Vanilla JS Remove id="submit" because of side effects: https://stackoverflow.com/questions/22982741/form-submit-jquery-does-not-work Fix arrow for login flow v1 Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>	4 年之前
Roeland Jago Douma	e6ac233947	Fix loginflow with apptoken enter on iOS It seems iOS doesn't like us to change the location. So now we submit it to the server that geneartes the redirect. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>	5 年之前
John Molakvoæ (skjnldsv)	5e4990fadd	Remove redirect page Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>	5 年之前
Mario Danic	e4aac15a92	Update login flow redirection Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	7 年之前
Morris Jobke	a9ccfe06d9	Fix some long lines in JS - JSLinut recommendation Signed-off-by: Morris Jobke <hey@morrisjobke.de>	7 年之前
Lukas Reschke	6a16df7288	Add new auth flow This implements the basics for the new app-password based authentication flow for our clients. The current implementation tries to keep it as simple as possible and works the following way: 1. Unauthenticated client opens `/index.php/login/flow` 2. User will be asked whether they want to grant access to the client 3. If accepted the user has the chance to do so using existing App Token or automatically generate an app password. If the user chooses to use an existing app token then that one will simply be redirected to the `nc://` protocol handler. While we can improve on that in the future, I think keeping this smaller at the moment has its advantages. Also, in the near future we have to think about an automatic migration endpoint so there's that anyways :-) If the user chooses to use the regular login the following happens: 1. A session state token is written to the session 2. User is redirected to the login page 3. If successfully authenticated they will be redirected to a page redirecting to the POST controller 4. The POST controller will check if the CSRF token as well as the state token is correct, if yes the user will be redirected to the `nc://` protocol handler. This approach is quite simple but also allows to be extended in the future. One could for example allow external websites to consume this authentication endpoint as well. Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	7 年之前

8 次程式碼提交 (a733a77f7bce2db0b4d4c529c843781f7379c4a8)