10 Commits (15ef354acec82b5d95642cfda95224ed34ffc8d0)

Author	SHA1	Message	Date
Morris Jobke	4ef302c0be	Request->getHeader() should always return a string ... PHPDoc (of the public API) says that this method returns string but it also returns null, which is not allowed in some method calls. This fixes that behaviour and returns an empty string and fixes all code paths that explicitly checked for null to be still compliant. Found while enabling the strict_typing for lib/private for the PHP7+ migration. Signed-off-by: Morris Jobke <hey@morrisjobke.de>	8 years ago
Joas Schilling	7789fbdea6	Add unit test ... Signed-off-by: Joas Schilling <coding@schilljs.com>	8 years ago
Bjoern Schiessle	555fe7047f	fix tests ... Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>	8 years ago
Mario Danic	c2cd5fc5d3	Fix flow ... Signed-off-by: Mario Danic <mario@lovelyhq.com>	8 years ago
Julius Härtl	cd1bfea8c4	Theming: theme flow redirection page ... Signed-off-by: Julius Härtl <jus@bitgrid.net>	8 years ago
Morris Jobke	444779ce96	Fix tests ... Signed-off-by: Morris Jobke <hey@morrisjobke.de>	8 years ago
Lukas Reschke	26ee889fec	Add tests for ClientFlowLoginController ... Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	9 years ago
Mario Danic	e4aac15a92	Update login flow redirection ... Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	9 years ago
Roeland Jago Douma	aae079aa29	AppToken to 72 chars ... Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>	9 years ago
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>	9 years ago