<cors> <allowed-origins> <origin>*</origin> </allowed-origins> <allowed-methods preflight-result-max-age=”300″> <method>*</method> </allowed-methods> <allowed-headers> <header>*</header> </allowed-headers> </cors>
Azure App Service Plan getting failed to be created. Getting the following error “Requested features are not supported in region. Please try another region” Solution:-Change the app service plan to something else, such as standard tier, and provision it should work! You can scale up… Read More
To debug Azure App Services or Azure Function apps, you can use the Connected Services or the Publish features available on all projects. If you rely on Visual Studio for publishing, you may access this feature under the “Additional Options” in the Hosting section. If… Read More
Classic Application Insights is deprecated and will be retired in February 2024.Migrate this resource to Workspace-based Application Insights to gain support for all of the capabilities of Log Analytics, including Customer-Managed Keys and Commitment Tiers.
Facing issues to get response back from REST API on Azure Active Directory B2C via custom policy (Identity Experience Framework)
How to create self signed TLS/SSL certificate? $cert = New-SelfSignedCertificate -CertStoreLocation cert:\currentuser\my -Subject “cn=asish.azure-api.net” -DnsName “rwf-npd.azure-api.net”$pwd = ConvertTo-SecureString -String ‘YourPassword’ -Force -AsPlainText$path = ‘cert:\currentuser\my\’ + $cert.thumbprintExport-PfxCertificate -cert $path -FilePath c:\test\powershellcert.pfx -Password $pwd Relevant for Azure API Management
The win2016 is deprecated. Any vs2017-win2016 runs will fail during the brownout period. Change the agent specification to windows latest will resolve the issue
To disable checking certificate revocation list use context.Request.Certificate.VerifyNoRevocation() instead of context.Request.Certificate.Verify(). If client certificate is self-signed, root (or intermediate) CA certificate(s) must be uploaded to API Management for context.Request.Certificate.Verify() and context.Request.Certificate.VerifyNoRevocation() to work.
openssl pkcs12 -in testcert.pfx -out C:\TLS\powershellcert.pem -nodes openssl pkcs12 -in testcert.pfx -nocerts -out [keyfilename-encrypted.key] Download and install openssl from https://slproweb.com/products/Win32OpenSSL.html
<validate-jwt header-name=”Authorization” failed-validation-httpcode=”401″ failed-validation-error-message=”Unauthorized. Access token is missing or invalid.”> <openid-config url=”https://xxxx.b2clogin.com/xxxx.onmicrosoft.com/v2.0/.well-known/openid-configuration?p=B2C_1A_SIGNUP_SIGNIN” /> <audiences> <audience>b33b3ba3-c921-4599-b648-57e9c5e023f</audience> </audiences> <issuers> <issuer>https://xxxx.b2clogin.com/a135e382-58b6-4d1e-8d7e-7323faa57809/v2.0/</issuer> </issuers> </validate-jwt>