forked-synapse/synapse/res/templates/sso_auth_bad_user.html

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="UTF-8">
        <title>Authentication failed</title>
        <meta name="viewport" content="width=device-width, user-scalable=no">
        <style type="text/css">
            {% include "sso.css" without context %}
        </style>
    </head>
    <body class="error_page">
        <header>
            <h1>That doesn't look right</h1>
            <p>
                <strong>We were unable to validate your {{ server_name }} account</strong>
                via single&nbsp;sign&#8209;on&nbsp;(SSO), because the SSO Identity
                Provider returned different details than when you logged in.
            </p>
            <p>
                Try the operation again, and ensure that you use the same details on
                the Identity Provider as when you log into your account.
            </p>
        </header>
        {% include "sso_footer.html" without context %}
    </body>
</html>
Improve styling and wording of SSO error templates (#9287) 2021-02-01 13:01:15 -05:00			`<!DOCTYPE html>`
			`<html lang="en">`
			`<head>`
			`<meta charset="UTF-8">`
			`<title>Authentication failed</title>`
			`<meta name="viewport" content="width=device-width, user-scalable=no">`
			`<style type="text/css">`
			`{% include "sso.css" without context %}`
			`</style>`
			`</head>`
			`<body class="error_page">`
			`<header>`
			`<h1>That doesn't look right</h1>`
Give the user a better error when they present bad SSO creds If a user tries to do UI Auth via SSO, but uses the wrong account on the SSO IdP, try to give them a better error. Previously, the UIA would claim to be successful, but then the operation in question would simply fail with "auth fail". Instead, serve up an error page which explains the failure. 2021-01-12 13:19:42 -05:00			`<p>`
Merge branch 'social_login' into develop 2021-02-01 13:46:12 -05:00			`<strong>We were unable to validate your {{ server_name }} account</strong>`
Improve styling and wording of SSO error templates (#9287) 2021-02-01 13:01:15 -05:00			`via single sign‑on (SSO), because the SSO Identity`
			`Provider returned different details than when you logged in.`
Give the user a better error when they present bad SSO creds If a user tries to do UI Auth via SSO, but uses the wrong account on the SSO IdP, try to give them a better error. Previously, the UIA would claim to be successful, but then the operation in question would simply fail with "auth fail". Instead, serve up an error page which explains the failure. 2021-01-12 13:19:42 -05:00			`</p>`
			`<p>`
			`Try the operation again, and ensure that you use the same details on`
			`the Identity Provider as when you log into your account.`
			`</p>`
Improve styling and wording of SSO error templates (#9287) 2021-02-01 13:01:15 -05:00			`</header>`
Social login UI polish (#9301) 2021-02-03 15:31:23 -05:00			`{% include "sso_footer.html" without context %}`
Give the user a better error when they present bad SSO creds If a user tries to do UI Auth via SSO, but uses the wrong account on the SSO IdP, try to give them a better error. Previously, the UIA would claim to be successful, but then the operation in question would simply fail with "auth fail". Instead, serve up an error page which explains the failure. 2021-01-12 13:19:42 -05:00			`</body>`
			`</html>`