Displaying 7 results from an estimated 7 matches for "root_ca".
2019 Dec 08
2
Dovecot & OAuth
...own as following in debug logs. I can confirming using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl -v https://<keycloak_server/' all returns normal and no errors. Altering some of the SSL options in dovecot such as 'ssl_ca = </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file = </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are NOT self-signed but signed the legit authorities. So I'm not sure why dovecot could not establish?the connections.
>>>>>>
2019 Dec 06
4
Dovecot & OAuth
...debug logs. I can confirming
> using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl
> -v https://<keycloak_server/' all returns normal and no errors. Altering
> some of the SSL options in dovecot such as 'ssl_ca =
> </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file =
> </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are
> NOT self-signed but signed the legit authorities. So I'm not sure why
> dovecot could not establish the connections.
> >
> > Debug logs:
> > ----...
2019 Dec 06
0
Dovecot & OAuth
...own as following in debug logs. I can confirming using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl -v https://<keycloak_server/' all returns normal and no errors. Altering some of the SSL options in dovecot such as 'ssl_ca = </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file = </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are NOT self-signed but signed the legit authorities. So I'm not sure why dovecot could not establish?the connections.
> > > > >
> > > >
2019 Dec 10
0
Dovecot & OAuth
...debug logs. I can confirming
> using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl
> -v https://<keycloak_server/' all returns normal and no errors. Altering
> some of the SSL options in dovecot such as 'ssl_ca =
> </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file =
> </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are
> NOT self-signed but signed the legit authorities. So I'm not sure why
> dovecot could not establish the connections.
> >>>>>>
>
>
------...
2019 Dec 05
2
Dovecot & OAuth
...own as following in debug logs. I can confirming
using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl
-v https://<keycloak_server/' all returns normal and no errors. Altering
some of the SSL options in dovecot such as 'ssl_ca =
</etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file =
</etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are
NOT self-signed but signed the legit authorities. So I'm not sure why
dovecot could not establish the connections.
*Debug logs:*
----------------------------------------------...
2019 Dec 05
0
Dovecot & OAuth
...own as following in debug logs. I can confirming using commands 'openssl s_client -connect <keycloak_server>:443' or 'curl -v https://<keycloak_server/' all returns normal and no errors. Altering some of the SSL options in dovecot such as 'ssl_ca = </etc/pki/CA/certs/root_ca.pem' or 'ssl_client_ca_file = </etc/pki/CA/certs/root_ca.pem' does not help either. The certificate are NOT self-signed but signed the legit authorities. So I'm not sure why dovecot could not establish?the connections.
>
> Debug logs:
> ---------------------------------...
2008 Jun 24
2
Suggestions for a plug and play CA certificate manager?
...gned root CA certificate,
then use that to issue one or more signing CA's, each possibly limited as
to what type of certificate that they can sign. These issuing CAs would
then sign certificate requests for end-use certificates for hosts, email
accounts, document provenance, objects, etc.
| -- root_CA
|
| -- issuer_hosts_a_CA
| | -- certs
| | | -- cert_issued_index
| | ` -- cert_revoked_list
| | -- csrs
| ` -- private
| ` -- issuer_hosts_a_CA+key.pem
|
| -- issuer_services_a_CA
| | -- certs
| | | --...