From 46a49fbb9d856452580e8ff07185a500ab4861f6 Mon Sep 17 00:00:00 2001 From: Martin Fischer Date: Thu, 13 Oct 2022 10:17:51 +0200 Subject: gracefully handle invalid usernames from ProviderDetails Previously we treated the case that a configured ProviderDetails returned an invalid username as an irrecoverable error but it makes more sense to just instead ask the user to pick a different username. --- i18n/en.json | 1 - 1 file changed, 1 deletion(-) (limited to 'i18n') diff --git a/i18n/en.json b/i18n/en.json index 7e5f74a..76bd20a 100644 --- a/i18n/en.json +++ b/i18n/en.json @@ -13,7 +13,6 @@ "redirectauth-collision-opt-create": "Create a new differently named account", "redirectauth-pick-other-username-taken": "The username $1 is already taken, please choose another username", "redirectauth-pick-other-username-invalid": "That username is invalid, please choose another username", - "redirectauth-error-invalid-username": "The configured $1 returned an invalid username", "redirectauth-linked-account": "Linked account:", "redirectauth-link-your": "Link your $1 account", "redirectauth-unlink-your": "Unlink your $1 account", -- cgit v1.2.3