8 Commits (73f256d91f3ce07e106e0ab0a506c640537124ff)

Author	SHA1	Message	Date
Michael Frister	ee31c8de7d	Omniauth: Add after_login, remove on_success ... After a successfull login seems to be a much clearer description of when the callback will be executed than "on successful authorization". E.g. it's not clear whether ending up on the registration page also indicates successful authorization (which it does in the OmniAuth sense, but not in the OpenProject sense). The after login callback is called each time a user is logged in, no matter whether that happens via regular Omniauth login or after completing the registration process and being automatically logged in (when automated account activation is enabled).	10 years ago
Markus Kahl	c798ebe878	pass auth_hash to #on_success. Call it upon bumpy registration too.	10 years ago
Markus Kahl	41603b0f43	on_success callback for Authorization	10 years ago
Markus Kahl	c430349640	updated comment	10 years ago
Markus Kahl	a20d471f2a	fixed default rejection; changed message	10 years ago
Markus Kahl	8ad54a544f	use decision store so that auth block doesn't necessarily have to return a Decision	10 years ago
Markus Kahl	fd1f8315cf	do not pass user into authorization callback	10 years ago
Markus Kahl	3303126657	OmniAuth Authorization API	10 years ago