docs/auth: remove insecure sign-in resolver recommendations

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>

docs/auth/atlassian/provider.md

@@ -49,9 +49,7 @@ auth:
         scope: ${AUTH_ATLASSIAN_SCOPES}
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/atlassian/provider#resolvers for more resolvers
             - resolver: usernameMatchingUserEntityName
 ```
 

docs/auth/aws-alb/provider.md

@@ -25,9 +25,8 @@ auth:
       region: 'us-west-2'
       signIn:
         resolvers:
-          # typically you would pick one of these
+          # See https://backstage.io/docs/auth/aws-alb/provider#resolvers for more resolvers
           - resolver: emailMatchingUserEntityProfileEmail
-          - resolver: emailLocalPartMatchingUserEntityName
 ```
 
 Ensure that you have set the signer correctly. It is also recommended that you restrict your target groups' security policy to only accept connections from that ALB.

docs/auth/bitbucket/provider.md

@@ -39,11 +39,8 @@ auth:
         clientSecret: ${AUTH_BITBUCKET_CLIENT_SECRET}
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/bitbucket/provider#resolvers for more resolvers
             - resolver: userIdMatchingUserEntityAnnotation
-            - resolver: usernameMatchingUserEntityAnnotation
 ```
 
 The Bitbucket provider is a structure with two configuration keys:

docs/auth/cloudflare/provider.md

@@ -41,8 +41,8 @@ auth:
       # This picks what sign in resolver(s) you want to use.
       signIn:
         resolvers:
+          # See https://backstage.io/docs/auth/cloudflare/provider#resolvers for more resolvers
           - resolver: emailMatchingUserEntityProfileEmail
-          - resolver: emailLocalPartMatchingUserEntityName
 ```
 
 This config section must be in place for the provider to load at all.

docs/auth/github/provider.md

@@ -51,8 +51,7 @@ auth:
         # enterpriseInstanceUrl: ${AUTH_GITHUB_ENTERPRISE_INSTANCE_URL}
         signIn:
           resolvers:
-            # Matches the GitHub username with the Backstage user entity name.
-            # See https://backstage.io/docs/auth/github/provider#resolvers for more resolvers.
+            # See https://backstage.io/docs/auth/github/provider#resolvers for more resolvers
             - resolver: usernameMatchingUserEntityName
 ```
 

docs/auth/gitlab/provider.md

@@ -46,9 +46,7 @@ auth:
         # callbackUrl: https://${BASE_URL}/api/auth/gitlab/handler/frame
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/gitlab/provider#resolvers for more resolvers
             - resolver: usernameMatchingUserEntityName
 ```
 

docs/auth/google/gcp-iap-auth.md

@@ -29,9 +29,7 @@ auth:
       jwtHeader: x-custom-header # Optional: Only if you are using a custom header for the IAP JWT
       signIn:
         resolvers:
-          # typically you would pick one of these
-          - resolver: emailMatchingUserEntityProfileEmail
-          - resolver: emailLocalPartMatchingUserEntityName
+          # See https://backstage.io/docs/auth/google/gcp-iap-auth#resolvers for more resolvers
           - resolver: emailMatchingUserEntityAnnotation
 ```
 

docs/auth/google/provider.md

@@ -44,9 +44,7 @@ auth:
         clientSecret: ${AUTH_GOOGLE_CLIENT_SECRET}
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/google/provider#resolvers for more resolvers
             - resolver: emailMatchingUserEntityAnnotation
 ```
 

docs/auth/microsoft/azure-easyauth.md

@@ -66,9 +66,7 @@ auth:
     azureEasyAuth:
       signIn:
         resolvers:
-          # typically you would pick one of these
-          - resolver: emailMatchingUserEntityProfileEmail
-          - resolver: emailLocalPartMatchingUserEntityName
+          # See https://backstage.io/docs/auth/microsoft/easy-auth#resolvers for more resolvers
           - resolver: idMatchingUserEntityAnnotation
 ```
 

docs/auth/microsoft/provider.md

@@ -69,10 +69,7 @@ auth:
         domainHint: ${AZURE_TENANT_ID}
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
-            - resolver: emailMatchingUserEntityAnnotation
+            # See https://backstage.io/docs/auth/microsoft/provider#resolvers for more resolvers
             - resolver: userIdMatchingUserEntityAnnotation
 ```
 

docs/auth/oauth2-proxy/provider.md

@@ -31,9 +31,7 @@ auth:
     oauth2Proxy:
       signIn:
         resolvers:
-          # typically you would pick one of these
-          - resolver: emailMatchingUserEntityProfileEmail
-          - resolver: emailLocalPartMatchingUserEntityName
+          # See https://backstage.io/docs/auth/oauth2-proxy/provider#resolvers for more resolvers
           - resolver: forwardedUserMatchingUserEntityName
 ```
 

docs/auth/oidc.md

@@ -156,8 +156,6 @@ auth:
         # ...
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailLocalPartMatchingUserEntityName
             - resolver: emailMatchingUserEntityProfileEmail
 ```
 

docs/auth/okta/provider.md

@@ -49,9 +49,7 @@ auth:
         additionalScopes: ${AUTH_OKTA_ADDITIONAL_SCOPES} # Optional
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/okta/provider#resolvers for more resolvers
             - resolver: emailMatchingUserEntityAnnotation
 ```
 

docs/auth/onelogin/provider.md

@@ -40,9 +40,7 @@ auth:
         issuer: https://<company>.onelogin.com/oidc/2
         signIn:
           resolvers:
-            # typically you would pick one of these
-            - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
+            # See https://backstage.io/docs/auth/onelogin/provider#resolvers for more resolvers
             - resolver: usernameMatchingUserEntityName
 ```
 

docs/auth/vmware-cloud/provider.md

@@ -49,10 +49,8 @@ auth:
         organizationId: ${ORG_ID}
         signIn:
           resolvers:
-            # typically you would pick one of these
+            # See https://backstage.io/docs/auth/vmware-cloud/provider#resolvers for more resolvers
             - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
-            - resolver: vmwareCloudSignInResolvers
 ```
 
 Where `APP_ID` refers to the ID retrieved when creating the OAuth App, and

docs/backend-system/building-backends/08-migrating.md

@@ -884,8 +884,6 @@ auth:
         signIn:
           resolvers:
             - resolver: emailMatchingUserEntityProfileEmail
-            - resolver: emailLocalPartMatchingUserEntityName
-            - resolver: emailMatchingUserEntityAnnotation
 ```
 
 :::note Note