nextcloud

Aborescence: 4983a35e1f

Auteur	SHA1	Message	Date
Marcel Müller	bbb490de5e	Fix event listener race condition on login-form Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>	il y a 1 an
Carl Schwan	3fa6ee3c60	Fix login flow Signed-off-by: Carl Schwan <carl@carlschwan.eu>	il y a 1 an
Carl Schwan	253118298d	Redesign guest pages for better accessibility - Use white box and put content on it - Improve focus indicator Signed-off-by: Carl Schwan <carl@carlschwan.eu>	il y a 1 an
Julius Härtl	61dd1d3d97	Pass username prefill through unauthenticated request redirects Signed-off-by: Julius Härtl <jus@bitgrid.net>	il y a 2 ans
Julius Härtl	cdda25acb4	Adjust auth token link design Signed-off-by: Julius Härtl <jus@bitgrid.net>	il y a 2 ans
Julius Härtl	aa3f4bdf63	Allow using an app token to login with v2 flow auth Signed-off-by: Julius Härtl <jus@bitgrid.net>	il y a 2 ans
Valdnet	2100b38f3c	Add a text string to l10n	il y a 3 ans
Lukas Reschke	6030dbe064	Move header into h3 Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	il y a 3 ans
Lukas Reschke	a1fe771a7d	Make security warning stand out more The security warning is currently being ignored by too many users as it's part of the text and not visually distinct. Ref #26944 Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	il y a 3 ans
Joas Schilling	abec8a2c63	Add a clear message why you could end up there Signed-off-by: Joas Schilling <coding@schilljs.com>	il y a 4 ans
Christoph Wurst	2fbad1ed72	Fix (array) indent style to always use one tab Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>	il y a 4 ans
Roeland Jago Douma	e819e97829	Login flow V2 This adds the new login flow. The desktop client will open up a browser and poll a returned endpoint at regular intervals to check if the flow is done. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>	il y a 5 ans
John Molakvoæ (skjnldsv)	5e4990fadd	Remove redirect page Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>	il y a 5 ans
Joas Schilling	ea21aa3f7a	Use numeric placeholders if there are multiple, so that RTL languages can operate better Signed-off-by: Joas Schilling <coding@schilljs.com>	il y a 5 ans
Roeland Jago Douma	177c8972cc	Improve login flow * Add page explaining you are about to grant access * Show grant access page after login Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>	il y a 6 ans
Roeland Jago Douma	f2d4c64c9a	Translate Grant Access Fixes #7038 Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>	il y a 6 ans
Morris Jobke	44c6745159	Remove quotes around device name Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 6 ans
Morris Jobke	bd43758118	Highlight client identifier in auth grant page Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 6 ans
Jan-Christoph Borchardt	ebdfcb1fe3	Add heading to account access page Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>	il y a 7 ans
Bjoern Schiessle	3775b14c4c	remove 'Alternative login using app token' in case of oauth login Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>	il y a 7 ans
Lukas Reschke	5f71805c35	Add basic implementation for OAuth 2.0 Authorization Code Flow Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	il y a 7 ans
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>	il y a 7 ans

13 Révisions (4983a35e1f7a176cc94fabea435552e0c73ec6bd)