Passing the DN of client's certificate to the deployed app in Tomcat
I configured Tomcat to require mutual authentication over TLS by setting clientAuth="true" in conf/server.xml file:
<Connector
port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150"
SSLEnabled="true"
scheme="https"
secure="true"
keystoreFile="conf/server.p12"
keystorePass="1t3TcUQY*2j^"
truststoreFile="conf/cacerts"
truststorePass="fx!eAKQO2^0c"
clientAuth="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2">
</Connector>
Everything is good, and Tomcat only accepts clients with valid certificates.
The problem is that the web app deployed in Tomcat has no idea of the identity of the client. By identity, I mean the subject info, such as its distinguished name (DN), that appears in the client's certificate. Therefore, the web app cannot make access control decisions based on the identity of the client.
Is there a way for Tomcat to pass this information to the deployed we app upon successful authentication?
security tomcat tls1.2 access-control client-certificates
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
add a comment |
I configured Tomcat to require mutual authentication over TLS by setting clientAuth="true" in conf/server.xml file:
<Connector
port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150"
SSLEnabled="true"
scheme="https"
secure="true"
keystoreFile="conf/server.p12"
keystorePass="1t3TcUQY*2j^"
truststoreFile="conf/cacerts"
truststorePass="fx!eAKQO2^0c"
clientAuth="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2">
</Connector>
Everything is good, and Tomcat only accepts clients with valid certificates.
The problem is that the web app deployed in Tomcat has no idea of the identity of the client. By identity, I mean the subject info, such as its distinguished name (DN), that appears in the client's certificate. Therefore, the web app cannot make access control decisions based on the identity of the client.
Is there a way for Tomcat to pass this information to the deployed we app upon successful authentication?
security tomcat tls1.2 access-control client-certificates
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
add a comment |
I configured Tomcat to require mutual authentication over TLS by setting clientAuth="true" in conf/server.xml file:
<Connector
port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150"
SSLEnabled="true"
scheme="https"
secure="true"
keystoreFile="conf/server.p12"
keystorePass="1t3TcUQY*2j^"
truststoreFile="conf/cacerts"
truststorePass="fx!eAKQO2^0c"
clientAuth="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2">
</Connector>
Everything is good, and Tomcat only accepts clients with valid certificates.
The problem is that the web app deployed in Tomcat has no idea of the identity of the client. By identity, I mean the subject info, such as its distinguished name (DN), that appears in the client's certificate. Therefore, the web app cannot make access control decisions based on the identity of the client.
Is there a way for Tomcat to pass this information to the deployed we app upon successful authentication?
security tomcat tls1.2 access-control client-certificates
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
I configured Tomcat to require mutual authentication over TLS by setting clientAuth="true" in conf/server.xml file:
<Connector
port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150"
SSLEnabled="true"
scheme="https"
secure="true"
keystoreFile="conf/server.p12"
keystorePass="1t3TcUQY*2j^"
truststoreFile="conf/cacerts"
truststorePass="fx!eAKQO2^0c"
clientAuth="true"
sslProtocol="TLS"
sslEnabledProtocols="TLSv1.2">
</Connector>
Everything is good, and Tomcat only accepts clients with valid certificates.
The problem is that the web app deployed in Tomcat has no idea of the identity of the client. By identity, I mean the subject info, such as its distinguished name (DN), that appears in the client's certificate. Therefore, the web app cannot make access control decisions based on the identity of the client.
Is there a way for Tomcat to pass this information to the deployed we app upon successful authentication?
security tomcat tls1.2 access-control client-certificates
security tomcat tls1.2 access-control client-certificates
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
asked Nov 16 at 6:22
M.S. Dousti
1,40942237
1,40942237
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Client certificates are accessible as
request.getAttribute("javax.servlet.request.X509Certificate")as an array of certificates. Read the Servlet Specification for the official reference. In Servlet 4.0 specification that is Chapter 3.10 SSL Attributes.
If your application is configured with
login-config/auth-methodofCLIENT-CERTthen an Authenticator in Tomcat will perform authentication of client certificate. The actual processing is delegated to a Realm.
If the authentication is successful, a user name is extracted from the certificate and a
java.security.Principalis created. Extraction of the user name is configurable with attributeX509UsernameRetrieverClassNameof the Realm. See Realm configuration reference.
(For reference, in Tomcat 9: org.apache.catalina.authenticator.SSLAuthenticator.doAuthenticate(), org.apache.catalina.realm.RealmBase.authenticate(X509Certificate))
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53332497%2fpassing-the-dn-of-clients-certificate-to-the-deployed-app-in-tomcat%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
Client certificates are accessible as
request.getAttribute("javax.servlet.request.X509Certificate")as an array of certificates. Read the Servlet Specification for the official reference. In Servlet 4.0 specification that is Chapter 3.10 SSL Attributes.
If your application is configured with
login-config/auth-methodofCLIENT-CERTthen an Authenticator in Tomcat will perform authentication of client certificate. The actual processing is delegated to a Realm.
If the authentication is successful, a user name is extracted from the certificate and a
java.security.Principalis created. Extraction of the user name is configurable with attributeX509UsernameRetrieverClassNameof the Realm. See Realm configuration reference.
(For reference, in Tomcat 9: org.apache.catalina.authenticator.SSLAuthenticator.doAuthenticate(), org.apache.catalina.realm.RealmBase.authenticate(X509Certificate))
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
add a comment |
Client certificates are accessible as
request.getAttribute("javax.servlet.request.X509Certificate")as an array of certificates. Read the Servlet Specification for the official reference. In Servlet 4.0 specification that is Chapter 3.10 SSL Attributes.
If your application is configured with
login-config/auth-methodofCLIENT-CERTthen an Authenticator in Tomcat will perform authentication of client certificate. The actual processing is delegated to a Realm.
If the authentication is successful, a user name is extracted from the certificate and a
java.security.Principalis created. Extraction of the user name is configurable with attributeX509UsernameRetrieverClassNameof the Realm. See Realm configuration reference.
(For reference, in Tomcat 9: org.apache.catalina.authenticator.SSLAuthenticator.doAuthenticate(), org.apache.catalina.realm.RealmBase.authenticate(X509Certificate))
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
add a comment |
Client certificates are accessible as
request.getAttribute("javax.servlet.request.X509Certificate")as an array of certificates. Read the Servlet Specification for the official reference. In Servlet 4.0 specification that is Chapter 3.10 SSL Attributes.
If your application is configured with
login-config/auth-methodofCLIENT-CERTthen an Authenticator in Tomcat will perform authentication of client certificate. The actual processing is delegated to a Realm.
If the authentication is successful, a user name is extracted from the certificate and a
java.security.Principalis created. Extraction of the user name is configurable with attributeX509UsernameRetrieverClassNameof the Realm. See Realm configuration reference.
(For reference, in Tomcat 9: org.apache.catalina.authenticator.SSLAuthenticator.doAuthenticate(), org.apache.catalina.realm.RealmBase.authenticate(X509Certificate))
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
Client certificates are accessible as
request.getAttribute("javax.servlet.request.X509Certificate")as an array of certificates. Read the Servlet Specification for the official reference. In Servlet 4.0 specification that is Chapter 3.10 SSL Attributes.
If your application is configured with
login-config/auth-methodofCLIENT-CERTthen an Authenticator in Tomcat will perform authentication of client certificate. The actual processing is delegated to a Realm.
If the authentication is successful, a user name is extracted from the certificate and a
java.security.Principalis created. Extraction of the user name is configurable with attributeX509UsernameRetrieverClassNameof the Realm. See Realm configuration reference.
(For reference, in Tomcat 9: org.apache.catalina.authenticator.SSLAuthenticator.doAuthenticate(), org.apache.catalina.realm.RealmBase.authenticate(X509Certificate))
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
answered Nov 19 at 9:51
Konstantin Kolinko
2,135514
2,135514
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53332497%2fpassing-the-dn-of-clients-certificate-to-the-deployed-app-in-tomcat%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
