In case of success, the protected resource requested by the client receives access from the server.įrom the server side view, if the client shows a certificate and uses the private key as part of a CertificateVerify message and the server validates the client certificate with regards to a set of trust anchors which does not include a hostile or incompetent root certificate authority (CA), then the server has a guarantee that it is addressing the right client.The server verifies the client’s credentials.In case of success, the client sends its certificate to the server.The client verifies the server’s certificate.The server sends its certificate to the client.
A client requests access to a protected resource.To establish an encrypted channel using the certificate-based two-way SSL: Two-way SSL authentication is known as client authentication or mutual authentication because the SSL client application sends its certificate to the SSL server once the SSL server has authenticated itself to the SSL client. If you require a certificate defined within a pre-approved domain, we can generate a CSR on behalf of your domain and use this for the Jira connector.We typically use our *. certificate for the validation process.Note: These are strict requirements because our application cannot support a subset of these. Our solution also requires access to the entire Jira REST API.
#Jira client side full
Our solution requires access to the full suite of REST verbs such as GET, POST, PUT, and DELETE.The SSL communication requirement is TLS 1.2.The Jira tier does the authentication per your recommended Jira authentication process to match your version of the Jira application.