silverstripe / silverstripe-framework

Completed

Push — master ( f862ce...9b1baa )

by Sam

created 2017-04-18 05:05 UTC

Changes

1036 issues (267 major, 669 minor, 100 informational) were introduced.
765 issues were fixed.

6.89

▶ ± 0

Head	Sam Minnee 2017-04-18 17:04 GMT+1200 DOCS: API changes from f862ce71d5b40e962569a23da957038d219b2967
Base	Simon Erkelens 2017-04-14 03:30 UTC Pass the AuthenticationMethod to the controller Resolves issue #6788 The AuthenticationMethed is passed in via hidden field as per usual, but due to changes, the fallback authenticator was always the MemberAuthenticator and the actual passed in authenticator was defaulting to an empty string. This causes an issue when there are multiple authenticators and the default authenticator is _not_ in the allowed authenticators, but is still the default. It caused the getAuthenticator method to return the default MemberAuthenticator to be returned, despite it being disabled. A second issue around multiple authenticators, was the template using a no-longer used method `getAuthenticatorName`. This method returned a null on the default MemberLoginForm (as nothing was set), causing a Warning. Because the getAuthenticator and getAuthenticatorName are no longer in use, I've opted to replace these with a translatable string `getAuthenticatorName`, to display the title of the form on the tabs, as per the tabset on Security_MultiAuthenticatorLogin template.