Thank you for the warm welcome !
Sure: The links are built in using the themes “Custom Header Links” component. They show up normally on nearly every page which is rendered by Discourse. They also show up for non-logged-in users even if the community is set private.
The instance uses the jonmbake’s ldap plugin for authentication only. It renders the login window by itself and is not customizable. If there would be multiple login methods enabled a selection would be displayed and there would be a button “Login with LDAP”, which opens an external login window. However i’m not allowed to do that as all users should be provided via LDAP. This leads to only LDAP-authentication-method left.
Previously, clicking on index page
http://discourse.examle.com just showed up a message like “You need to login to see that page. […]” rendered by Discourse. If the user needed to reset his password, he could just click the link showed by “Custom Header Links” component. Now the behavior is different and the user does not see the Discourse page but instead gets directly redirected to the external login page. This causes issues as i can not modify that page (and put there a password reset link).
ah i found even the change notification in the changelog:
- Automatically redirect to authenticator when there is only one
from there: Discourse 2.4.0.beta8 Release Notes