discourse/app/views/session/sso_login.html.erb

<h1><%= t('discourse_connect.login_error') %></h1>

<br/>

<p><%=raw @sso_error %></p>
FEATURE: Rename 'Discourse SSO' to DiscourseConnect (#11978) The 'Discourse SSO' protocol is being rebranded to DiscourseConnect. This should help to reduce confusion when 'SSO' is used in the generic sense. This commit aims to: - Rename `sso_` site settings. DiscourseConnect specific ones are prefixed `discourse_connect_`. Generic settings are prefixed `auth_` - Add (server-side-only) backwards compatibility for the old setting names, with deprecation notices - Copy `site_settings` database records to the new names - Rename relevant translation keys - Update relevant translations This commit does not aim to: - Rename any Ruby classes or methods. This might be done in a future commit - Change any URLs. This would break existing integrations - Make any changes to the protocol. This would break existing integrations - Change any functionality. Further normalization across DiscourseConnect and other auth methods will be done separately The risks are: - There is no backwards compatibility for site settings on the client-side. Accessing auth-related site settings in Javascript is fairly rare, and an error on the client side would not be security-critical. - If a plugin is monkey-patching parts of the auth process, changes to locale keys could cause broken error messages. This should also be unlikely. The old site setting names remain functional, so security-related overrides will remain working. A follow-up commit will be made with a post-deploy migration to delete the old `site_settings` rows. 2021-02-08 05:04:33 -05:00			`<h1><%= t('discourse_connect.login_error') %></h1>`
Render a layout when there's an SSO error 2017-03-21 14:04:25 -04:00
Custom errors for when Email is invalid via SSO 2017-03-21 14:37:21 -04:00			`<br/>`

Display email address in SSO error message. 2017-03-21 15:37:46 -04:00			`<p><%=raw @sso_error %></p>`