ssl-certificate

Kubernetes doesnt create certificates

假如想象 提交于 2021-01-29 09:00:36
问题 I've created my certificate cfssl but when I generate my Kubernetes certificates with the file generated by cfssl, my Kubernetes returns the following error: Error from server (BadRequest): error when creating "certificado.yml": CertificateSigningRequest in version "v1beta1" cannot be handled as a CertificateSigningRequest: v1beta1.CertificateSigningRequest.Spec: v1beta1.CertificateSigningRequestSpec.Usages: []v1beta1.KeyUsage: Request: decode base64: illegal base64 data at input byte 3,

ActiveMQ SSL - Reload truststore with out restart broker

自闭症网瘾萝莉.ら 提交于 2021-01-29 07:29:17
问题 Im using activeMQ as my messages server. In order to keep it secure between the server and the clients (producer/consumer), I added to the activemq.xml a ssl context section that tells the activemq when it starts, with which keystore and truststore file to use. In case the truststore has be updated with a new certifiate, I would like the activemq to reload the truststore without restart the broker itself. Is there any way t do it? I found something similer in the link below but I don't know

Why i need to type HTTPS manually to access my site?

拜拜、爱过 提交于 2021-01-29 05:40:47
问题 why do I need to type https before my site URL every time in the browser? Tho my website has SSL enabled it's going to default IIS page. Please help me with this. This url i'm typing in browser -- fdrms.visiontek.co.in/ If I want to see my SSL enabled page every time I need to add https:// before above URL like -- https://fdrms.visiontek.co.in/ 回答1: Once the SSL certificate is installed, your site still remains accessible via a regular insecure HTTP connection. To connect secure url you need

ASP.Net Core docker access serviceA container from serviceB container throws ssl certificate error

 ̄綄美尐妖づ 提交于 2021-01-28 19:44:34
问题 I am developing a Web Application with Microservice Architecture. I use docker and docker-compose to run my microservices. I want to access an api from the frontend service. But it always throws SSL certificate exception, whichs tell me that the issuer is not verified from curl. I get this error from the HttpClient in my demo MVC app: "The remote certificate is invalid according to the validation procedure." I created a demo project for testing it, here is the github link: https://github.com

Certificate issue in Kestrel ssl JSON configuration using .net Core 3.1

Deadly 提交于 2021-01-28 11:45:54
问题 I have seen this question answered but it doesn't seem to be working for .net core 3.1 This code finds the Certificate: using (var store = new X509Store("Root", StoreLocation.LocalMachine)) { store.Open(OpenFlags.ReadOnly); var certCollection = store.Certificates; var currentCerts = certCollection.Find(X509FindType.FindBySubjectName, "*.timedesk.com", false); if (currentCerts.Count == 0) throw new Exception("Https certificate is not found."); } This appsettings.json does not find the

Certificate issue in Kestrel ssl JSON configuration using .net Core 3.1

微笑、不失礼 提交于 2021-01-28 11:39:50
问题 I have seen this question answered but it doesn't seem to be working for .net core 3.1 This code finds the Certificate: using (var store = new X509Store("Root", StoreLocation.LocalMachine)) { store.Open(OpenFlags.ReadOnly); var certCollection = store.Certificates; var currentCerts = certCollection.Find(X509FindType.FindBySubjectName, "*.timedesk.com", false); if (currentCerts.Count == 0) throw new Exception("Https certificate is not found."); } This appsettings.json does not find the

Create Self Signed Certificate with Subject Key Identifier

大城市里の小女人 提交于 2021-01-28 07:43:19
问题 I want to create a self signed certificate with RSA algorithm keysize 2048 with subject key identifier. I know we made some some default change in openssl.conf . What i suppose to change? genrsa -des3 -out mcedt.key 2048 req -new -key mcedt.key -out mcedt.csr CN = server.test , OU =, O =, L = Toronto, S = ontario , C = can x509 -req -days 365 -in mcedt.csr -signkey mcedt.key -out mcedt.crt pkcs12 -export -in mcedt.crt -inkey mcedt.key -out mcedt.pfx 回答1: You could create an extension file

docker (behind a proxy) pull from azure container registry works but from registry-1.docker.io, it gives certificate signed by unknown authority error

青春壹個敷衍的年華 提交于 2021-01-28 05:15:18
问题 In ubuntu 18.04 VM I am behind a proxy, I've set up docker configuration with the same proxy. I created an azure container registry and when trying to docker pull from the registry it works. But when trying to: $docker run node:6 I get the error: "docker: Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate signed by unknown authority." I've added the registry to /etc/docker/daemon.json: { "insecure-registries": ["registry-1.docker.io","myazureContainerRegistry

The request was aborted: Could not create SSL/TLS secure channel - IllegalMessage

大城市里の小女人 提交于 2021-01-27 18:53:24
问题 I have seen few similar questions regarding this topic on SO, but it seems that none of the answers really helps to resolve it. I need to reach customer webservice with certificate authentication. It works fine using SoapUI and chrome after selecting correct certificate when prompted. But I am not able to reach the service with IE, WCF client, not my own, nor WcfTestClient. OS is Windows server 2012 R2, protocol TLS 1.2 I have been investigating events, tracelogs, also spend quite some time

.NET Core gives unknown error while processing HTTPS certificate [closed]

|▌冷眼眸甩不掉的悲伤 提交于 2021-01-27 14:31:43
问题 Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 1 year ago . Improve this question I'm trying to build a .NET Core server that uses a HTTPS connection. I created a self-signed certificate using dotnet dev-certs tool and set up Kestrel like this: return WebHost.CreateDefaultBuilder(args) .UseKestrel(options => { options.Listen(IPAddress