Never expose the SecretKey to the public outside of the assembly. Red…

…uces risk of using it as the SiteKey on a view by accident.
griesoft · Feb 19, 2020 · 81fff5a · 81fff5a
1 parent d707ab9
commit 81fff5a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/src/ReCaptcha/Configuration/RecaptchaSettings.cs b/src/ReCaptcha/Configuration/RecaptchaSettings.cs
@@ -4,6 +4,6 @@ public class RecaptchaSettings
     {
         public string SiteKey { get; set; } = string.Empty;
 
-        public string SecretKey { get; set; } = string.Empty;
+        internal string SecretKey { get; set; } = string.Empty;
     }
 }
diff --git a/src/ReCaptcha/Extensions/RecaptchaServiceExtensions.cs b/src/ReCaptcha/Extensions/RecaptchaServiceExtensions.cs
@@ -17,7 +17,8 @@ public static IServiceCollection AddRecaptchaService(this IServiceCollection ser
         {
             services.AddOptions<RecaptchaSettings>()
                 .Configure<IConfiguration>((settings, config) =>
-                    config.GetSection(RecaptchaServiceConstants.SettingsSectionKey).Bind(settings));
+                    config.GetSection(RecaptchaServiceConstants.SettingsSectionKey)
+                    .Bind(settings, (op) => op.BindNonPublicProperties = true));
 
             services.Configure(options ??= opt => { });