Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide design for Tomcat Realm based authentication/authorization #585

Closed
pki-bot opened this issue Oct 2, 2020 · 4 comments
Closed

Provide design for Tomcat Realm based authentication/authorization #585

pki-bot opened this issue Oct 2, 2020 · 4 comments

Comments

@pki-bot
Copy link

pki-bot commented Oct 2, 2020

This issue was migrated from Pagure Issue #13. Originally filed by jmagne (@jmagne) on 2011-11-15 03:14:37:


Based on results of requirements gathering, come up with a design on how to actually accomplish the required functionality.

@pki-bot pki-bot added this to the Dogtag 10.0.0.a1 milestone Oct 2, 2020
@pki-bot pki-bot closed this as completed Oct 2, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from jmagne (@jmagne) at 2011-11-22 20:05:31

Experimented with a sample JNDI realm hooked up with the "CLIENT-CERTS" authentication method. This was done using tomcatjss at the connector level. Going to the page asks for the cert. Research indicates that there is a way to create a custom JNDI tomcat Realm that overrrides the getPricipal(X509Cert certs) method. We could add code to both make use of the JNDI realm and actually compare the incoming cert to the cert in the LDAP database already encoded.

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from jmagne (@jmagne) at 2011-12-06 20:46:35

Progress:

Was able to put together a rough custom JNDI realm hooked up to our tomcatjss SSL Connector port. The realm does nothing but override "getPrincipal(X509Cert usercert) and extracts the uid of the incoming user from the cert's subject name.That uid is sent into getPrincipal(String username). The JNDI part of the realm is configured simply to search for the user from a base dn using a simple search pattern.

The next step is to put in some code to do the certificate comparison that we do in our system already.

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from jmagne (@jmagne) at 2012-01-19 19:43:01

The solid concept it here. There will be a bit more investigation to finish this off.

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from jmagne (@jmagne) at 2017-02-27 14:08:23

Metadata Update from @jmagne:

  • Issue assigned to jmagne
  • Issue set to the milestone: Dogtag 10.0.0.a1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant