7 Commits (03c6fcdf6f8fcecf98caa413897cea83e7802b7e)

Author	SHA1	Message	Date
Alex Coles	e0191e759c	Update year in copyright header to 2015 ... [ci skip]	10 years ago
Alex Coles	5afc11f19e	Fix syntax (w/Rubocop) in specs ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Martin Linkhorst	a2754921dd	make Hound happy (and Markus)	10 years ago
Martin Linkhorst	c43f84ad1b	#after_login can now receive a context variable (usually the controller)	10 years ago
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