Identity Server 3 - Posted data for token endpoint not read











up vote
0
down vote

favorite












I have a strange problem for an application I put in production.



The app is a Asp.net 4.7.2 Webapi protected by an embedded Identity Server 3 instance plus an instance of swagger for documentation.



I need only client authentication so I choose client credential as flow.



These are the main configuration data for the application.



new Client {
ClientName = "GDPR Logger Client",
Enabled = true,
ClientId = "gdpr_logger",
Flow = Flows.ClientCredentials,
AccessTokenType = AccessTokenType.Reference,
ClientSecrets = new List<Secret> {
new Secret("secret".Sha256())
},
AllowedScopes = new List<string> {
"write"
},
AccessTokenLifetime = 30
}

app.Map("/auth", auth => {
var options = new IdentityServerOptions {
SiteName = "GDPR LOGGER Authentication Server",
SigningCertificate = LoadCertificate(),
RequireSsl = true,
Factory = new IdentityServerServiceFactory()
.UseInMemoryUsers(new List<InMemoryUser>())
.UseInMemoryClients(Clients.Get())
.UseInMemoryScopes(Scopes.Get());
};
auth.UseIdentityServer(options);
});

private static X509Certificate2 LoadCertificate() {
certificateFilePath = HttpContext.Current.Server.MapPath(ConfigurationManager.AppSettings["RelativeCertPath"]);
X509Certificate2 cert = new X509Certificate2();
cert.Import(certificateFilePath, "GDPRLoggerCert", X509KeyStorageFlags.PersistKeySet | X509KeyStorageFlags.MachineKeySet);
return cert;}


In my local machine all work perfect, but as soon I put it on my server the Identity Server stop working.



When I try to get the access token for the client (with client_credentials flow) Identity Server respond me with invalid_client when I POST to https://{my-server}/auth/connect/token all data as application/x-www-form-urlencoded content in the request grant_type=client_credentials&client_id=gdpr_logger&client_secret=secret&scope=write.



2018-11-20 09:14:20,035 [244] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - Start parsing for secret in post body
2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - No secret in post body found
2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - Start parsing for X.509 certificate
2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - client_id is not found in post body
2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.SecretParser - Parser found no secret
2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.ClientSecretValidator - No client secret found
2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
2018-11-20 09:14:20,097 [244] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: invalid_client


If I specify client_id and client_secret as Basic Authentication Header Identity server respond me with unsupported_grant_type.



2018-11-20 09:08:36,113 [323] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.SecretParser - Parser found secret: BasicAuthenticationSecretParser
2018-11-20 09:08:36,144 [323] INFO IdentityServer3.Core.Validation.SecretParser - Secret id found: gdpr_logger
2018-11-20 09:08:36,160 [323] DEBUG IdentityServer3.Core.Validation.SecretValidator - Secret validator success: HashedSharedSecretValidator
2018-11-20 09:08:36,160 [323] INFO IdentityServer3.Core.Validation.ClientSecretValidator - Client validation success
2018-11-20 09:08:36,176 [323] INFO IdentityServer3.Core.Validation.TokenRequestValidator - Start token request validation
2018-11-20 09:08:36,363 [323] ERROR IdentityServer3.Core.Validation.TokenRequestValidator - Grant type is missing.
{
"ClientId": "gdpr_logger",
"ClientName": "GDPR Logger Client",
"Raw": {}
}
2018-11-20 09:08:36,363 [323] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
2018-11-20 09:08:36,379 [323] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: unsupported_grant_type


As you can see in the last log in Raw it seems the data in post are not read/picked up from Identity Server.



I cannot understand what is the problem.










share|improve this question


























    up vote
    0
    down vote

    favorite












    I have a strange problem for an application I put in production.



    The app is a Asp.net 4.7.2 Webapi protected by an embedded Identity Server 3 instance plus an instance of swagger for documentation.



    I need only client authentication so I choose client credential as flow.



    These are the main configuration data for the application.



    new Client {
    ClientName = "GDPR Logger Client",
    Enabled = true,
    ClientId = "gdpr_logger",
    Flow = Flows.ClientCredentials,
    AccessTokenType = AccessTokenType.Reference,
    ClientSecrets = new List<Secret> {
    new Secret("secret".Sha256())
    },
    AllowedScopes = new List<string> {
    "write"
    },
    AccessTokenLifetime = 30
    }

    app.Map("/auth", auth => {
    var options = new IdentityServerOptions {
    SiteName = "GDPR LOGGER Authentication Server",
    SigningCertificate = LoadCertificate(),
    RequireSsl = true,
    Factory = new IdentityServerServiceFactory()
    .UseInMemoryUsers(new List<InMemoryUser>())
    .UseInMemoryClients(Clients.Get())
    .UseInMemoryScopes(Scopes.Get());
    };
    auth.UseIdentityServer(options);
    });

    private static X509Certificate2 LoadCertificate() {
    certificateFilePath = HttpContext.Current.Server.MapPath(ConfigurationManager.AppSettings["RelativeCertPath"]);
    X509Certificate2 cert = new X509Certificate2();
    cert.Import(certificateFilePath, "GDPRLoggerCert", X509KeyStorageFlags.PersistKeySet | X509KeyStorageFlags.MachineKeySet);
    return cert;}


    In my local machine all work perfect, but as soon I put it on my server the Identity Server stop working.



    When I try to get the access token for the client (with client_credentials flow) Identity Server respond me with invalid_client when I POST to https://{my-server}/auth/connect/token all data as application/x-www-form-urlencoded content in the request grant_type=client_credentials&client_id=gdpr_logger&client_secret=secret&scope=write.



    2018-11-20 09:14:20,035 [244] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
    2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
    2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
    2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - Start parsing for secret in post body
    2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - No secret in post body found
    2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - Start parsing for X.509 certificate
    2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - client_id is not found in post body
    2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.SecretParser - Parser found no secret
    2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.ClientSecretValidator - No client secret found
    2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
    2018-11-20 09:14:20,097 [244] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: invalid_client


    If I specify client_id and client_secret as Basic Authentication Header Identity server respond me with unsupported_grant_type.



    2018-11-20 09:08:36,113 [323] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
    2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
    2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
    2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.SecretParser - Parser found secret: BasicAuthenticationSecretParser
    2018-11-20 09:08:36,144 [323] INFO IdentityServer3.Core.Validation.SecretParser - Secret id found: gdpr_logger
    2018-11-20 09:08:36,160 [323] DEBUG IdentityServer3.Core.Validation.SecretValidator - Secret validator success: HashedSharedSecretValidator
    2018-11-20 09:08:36,160 [323] INFO IdentityServer3.Core.Validation.ClientSecretValidator - Client validation success
    2018-11-20 09:08:36,176 [323] INFO IdentityServer3.Core.Validation.TokenRequestValidator - Start token request validation
    2018-11-20 09:08:36,363 [323] ERROR IdentityServer3.Core.Validation.TokenRequestValidator - Grant type is missing.
    {
    "ClientId": "gdpr_logger",
    "ClientName": "GDPR Logger Client",
    "Raw": {}
    }
    2018-11-20 09:08:36,363 [323] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
    2018-11-20 09:08:36,379 [323] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: unsupported_grant_type


    As you can see in the last log in Raw it seems the data in post are not read/picked up from Identity Server.



    I cannot understand what is the problem.










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a strange problem for an application I put in production.



      The app is a Asp.net 4.7.2 Webapi protected by an embedded Identity Server 3 instance plus an instance of swagger for documentation.



      I need only client authentication so I choose client credential as flow.



      These are the main configuration data for the application.



      new Client {
      ClientName = "GDPR Logger Client",
      Enabled = true,
      ClientId = "gdpr_logger",
      Flow = Flows.ClientCredentials,
      AccessTokenType = AccessTokenType.Reference,
      ClientSecrets = new List<Secret> {
      new Secret("secret".Sha256())
      },
      AllowedScopes = new List<string> {
      "write"
      },
      AccessTokenLifetime = 30
      }

      app.Map("/auth", auth => {
      var options = new IdentityServerOptions {
      SiteName = "GDPR LOGGER Authentication Server",
      SigningCertificate = LoadCertificate(),
      RequireSsl = true,
      Factory = new IdentityServerServiceFactory()
      .UseInMemoryUsers(new List<InMemoryUser>())
      .UseInMemoryClients(Clients.Get())
      .UseInMemoryScopes(Scopes.Get());
      };
      auth.UseIdentityServer(options);
      });

      private static X509Certificate2 LoadCertificate() {
      certificateFilePath = HttpContext.Current.Server.MapPath(ConfigurationManager.AppSettings["RelativeCertPath"]);
      X509Certificate2 cert = new X509Certificate2();
      cert.Import(certificateFilePath, "GDPRLoggerCert", X509KeyStorageFlags.PersistKeySet | X509KeyStorageFlags.MachineKeySet);
      return cert;}


      In my local machine all work perfect, but as soon I put it on my server the Identity Server stop working.



      When I try to get the access token for the client (with client_credentials flow) Identity Server respond me with invalid_client when I POST to https://{my-server}/auth/connect/token all data as application/x-www-form-urlencoded content in the request grant_type=client_credentials&client_id=gdpr_logger&client_secret=secret&scope=write.



      2018-11-20 09:14:20,035 [244] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
      2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
      2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - Start parsing for secret in post body
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - No secret in post body found
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - Start parsing for X.509 certificate
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - client_id is not found in post body
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.SecretParser - Parser found no secret
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.ClientSecretValidator - No client secret found
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
      2018-11-20 09:14:20,097 [244] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: invalid_client


      If I specify client_id and client_secret as Basic Authentication Header Identity server respond me with unsupported_grant_type.



      2018-11-20 09:08:36,113 [323] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.SecretParser - Parser found secret: BasicAuthenticationSecretParser
      2018-11-20 09:08:36,144 [323] INFO IdentityServer3.Core.Validation.SecretParser - Secret id found: gdpr_logger
      2018-11-20 09:08:36,160 [323] DEBUG IdentityServer3.Core.Validation.SecretValidator - Secret validator success: HashedSharedSecretValidator
      2018-11-20 09:08:36,160 [323] INFO IdentityServer3.Core.Validation.ClientSecretValidator - Client validation success
      2018-11-20 09:08:36,176 [323] INFO IdentityServer3.Core.Validation.TokenRequestValidator - Start token request validation
      2018-11-20 09:08:36,363 [323] ERROR IdentityServer3.Core.Validation.TokenRequestValidator - Grant type is missing.
      {
      "ClientId": "gdpr_logger",
      "ClientName": "GDPR Logger Client",
      "Raw": {}
      }
      2018-11-20 09:08:36,363 [323] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
      2018-11-20 09:08:36,379 [323] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: unsupported_grant_type


      As you can see in the last log in Raw it seems the data in post are not read/picked up from Identity Server.



      I cannot understand what is the problem.










      share|improve this question













      I have a strange problem for an application I put in production.



      The app is a Asp.net 4.7.2 Webapi protected by an embedded Identity Server 3 instance plus an instance of swagger for documentation.



      I need only client authentication so I choose client credential as flow.



      These are the main configuration data for the application.



      new Client {
      ClientName = "GDPR Logger Client",
      Enabled = true,
      ClientId = "gdpr_logger",
      Flow = Flows.ClientCredentials,
      AccessTokenType = AccessTokenType.Reference,
      ClientSecrets = new List<Secret> {
      new Secret("secret".Sha256())
      },
      AllowedScopes = new List<string> {
      "write"
      },
      AccessTokenLifetime = 30
      }

      app.Map("/auth", auth => {
      var options = new IdentityServerOptions {
      SiteName = "GDPR LOGGER Authentication Server",
      SigningCertificate = LoadCertificate(),
      RequireSsl = true,
      Factory = new IdentityServerServiceFactory()
      .UseInMemoryUsers(new List<InMemoryUser>())
      .UseInMemoryClients(Clients.Get())
      .UseInMemoryScopes(Scopes.Get());
      };
      auth.UseIdentityServer(options);
      });

      private static X509Certificate2 LoadCertificate() {
      certificateFilePath = HttpContext.Current.Server.MapPath(ConfigurationManager.AppSettings["RelativeCertPath"]);
      X509Certificate2 cert = new X509Certificate2();
      cert.Import(certificateFilePath, "GDPRLoggerCert", X509KeyStorageFlags.PersistKeySet | X509KeyStorageFlags.MachineKeySet);
      return cert;}


      In my local machine all work perfect, but as soon I put it on my server the Identity Server stop working.



      When I try to get the access token for the client (with client_credentials flow) Identity Server respond me with invalid_client when I POST to https://{my-server}/auth/connect/token all data as application/x-www-form-urlencoded content in the request grant_type=client_credentials&client_id=gdpr_logger&client_secret=secret&scope=write.



      2018-11-20 09:14:20,035 [244] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
      2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
      2018-11-20 09:14:20,066 [244] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - Start parsing for secret in post body
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.PostBodySecretParser - No secret in post body found
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - Start parsing for X.509 certificate
      2018-11-20 09:14:20,082 [244] DEBUG IdentityServer3.Core.Validation.X509CertificateSecretParser - client_id is not found in post body
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.SecretParser - Parser found no secret
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Validation.ClientSecretValidator - No client secret found
      2018-11-20 09:14:20,082 [244] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
      2018-11-20 09:14:20,097 [244] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: invalid_client


      If I specify client_id and client_secret as Basic Authentication Header Identity server respond me with unsupported_grant_type.



      2018-11-20 09:08:36,113 [323] INFO  IdentityServer3.Core.Endpoints.TokenEndpointController - Start token request
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.ClientSecretValidator - Start client validation
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.BasicAuthenticationSecretParser - Start parsing Basic Authentication secret
      2018-11-20 09:08:36,144 [323] DEBUG IdentityServer3.Core.Validation.SecretParser - Parser found secret: BasicAuthenticationSecretParser
      2018-11-20 09:08:36,144 [323] INFO IdentityServer3.Core.Validation.SecretParser - Secret id found: gdpr_logger
      2018-11-20 09:08:36,160 [323] DEBUG IdentityServer3.Core.Validation.SecretValidator - Secret validator success: HashedSharedSecretValidator
      2018-11-20 09:08:36,160 [323] INFO IdentityServer3.Core.Validation.ClientSecretValidator - Client validation success
      2018-11-20 09:08:36,176 [323] INFO IdentityServer3.Core.Validation.TokenRequestValidator - Start token request validation
      2018-11-20 09:08:36,363 [323] ERROR IdentityServer3.Core.Validation.TokenRequestValidator - Grant type is missing.
      {
      "ClientId": "gdpr_logger",
      "ClientName": "GDPR Logger Client",
      "Raw": {}
      }
      2018-11-20 09:08:36,363 [323] INFO IdentityServer3.Core.Endpoints.TokenEndpointController - End token request
      2018-11-20 09:08:36,379 [323] INFO IdentityServer3.Core.Results.TokenErrorResult - Returning error: unsupported_grant_type


      As you can see in the last log in Raw it seems the data in post are not read/picked up from Identity Server.



      I cannot understand what is the problem.







      iis identityserver3 production






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 at 8:42









      Angelo Rotta

      11




      11
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          My Server manager solved the problem.



          The ModSecurity (in Plesk inside the Web Application Firewall) for a second level domain as in my case blocked the post data because is againt its rules.



          Disabling or editing the rules solved the problem.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389131%2fidentity-server-3-posted-data-for-token-endpoint-not-read%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            My Server manager solved the problem.



            The ModSecurity (in Plesk inside the Web Application Firewall) for a second level domain as in my case blocked the post data because is againt its rules.



            Disabling or editing the rules solved the problem.






            share|improve this answer

























              up vote
              0
              down vote













              My Server manager solved the problem.



              The ModSecurity (in Plesk inside the Web Application Firewall) for a second level domain as in my case blocked the post data because is againt its rules.



              Disabling or editing the rules solved the problem.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                My Server manager solved the problem.



                The ModSecurity (in Plesk inside the Web Application Firewall) for a second level domain as in my case blocked the post data because is againt its rules.



                Disabling or editing the rules solved the problem.






                share|improve this answer












                My Server manager solved the problem.



                The ModSecurity (in Plesk inside the Web Application Firewall) for a second level domain as in my case blocked the post data because is againt its rules.



                Disabling or editing the rules solved the problem.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 20 at 8:58









                Angelo Rotta

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389131%2fidentity-server-3-posted-data-for-token-endpoint-not-read%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Tonle Sap (See)

                    I get strange results when I access the Sqlitedatabase with Unity C# via XAMPP

                    Guatemaltekische Davis-Cup-Mannschaft