On Thu, Jul 20, 2023 at 12:30 PM Felix Schumacher
wrote:
>
>
> Am 20.07.23 um 11:40 schrieb Rémy Maucherat:
>
> On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher
> wrote:
>
> Hi all,
>
> at work, we have seen the following stacktrace without a retrying log message.
>
> javax.naming.NamingExceptio
Am 20.07.23 um 11:40 schrieb Rémy Maucherat:
On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher
wrote:
Hi all,
at work, we have seen the following stacktrace without a retrying log message.
javax.naming.NamingException: LDAP connection has been closed
at com.sun.jndi.ldap.LdapRequest.ge
On Thu, Jul 20, 2023 at 11:11 AM Felix Schumacher
wrote:
>
> Hi all,
>
> at work, we have seen the following stacktrace without a retrying log message.
>
> javax.naming.NamingException: LDAP connection has been closed
> at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133)
> ~[?:
Jess,
https://issues.apache.org/bugzilla/show_bug.cgi?id=57208
On 11/14/14 2:25 PM, Jess Holle wrote:
> I just moved from Tomcat 7.0.56 to 8.0.15.
>
> I tried out form-based authentication using CombinedRealm of 2 JNDIRealms.
>
> I get:
>
> java.lang.NullPointerException
> org.apache.catal
Jess,
On 11/14/14 2:25 PM, Jess Holle wrote:
> I just moved from Tomcat 7.0.56 to 8.0.15.
>
> I tried out form-based authentication using CombinedRealm of 2 JNDIRealms.
>
> I get:
>
> java.lang.NullPointerException
> org.apache.catalina.realm.JNDIRealm.getUser(JNDIRealm.java:1286)
> org
Konstantin,
On 2/14/12 6:55 PM, Konstantin Kolinko wrote:
> I wonder whether anyone experienced problems with performance of JNDIRealm.
>
> In essence it opens a single connection (this.context) which is not
> thread-safe. Thus it has to synchronize itself whenever it performs an
> LDAP query.
On 28/09/2010 21:20, Wick Swain wrote:
> We have made a change to account for this in the JNDIRealm class. What would
> we have to do to have this considered for inclusion in the next version of
> Tomcat?
Create a Bugzilla entry and attach a patch in diff -u format. Ideally
against trunk. Against
I just noticed this email thread on the Tomcat dev list. If a bug was
filed with the patch, could somebody add me to the Bugzilla CC or give
me the bug ID? Thanks,
-- Seth
Mark Thomas wrote:
william.be...@accenture.com wrote:
Hi Tomcat Developers,
I have updated the patch from http://m
[EMAIL PROTECTED] wrote:
> Hi Tomcat Developers,
> I have updated the patch from http://markmail.org/message/qrmrubh3gfrz5yo5
> to
> match up with the current source release for tomcat 6.0.18. I am interested
> in getting this patch applied to the code base. So, I am curious if anything
>
Hi Tomcat Developers,
I have updated the patch from http://markmail.org/message/qrmrubh3gfrz5yo5 to
match up with the current source release for tomcat 6.0.18. I am interested
in getting this patch applied to the code base. So, I am curious if anything
else needs to be done?
Thanks,
Will
This patch will have some offset problems because it's off of my working
copy of the JNDIRealm class. But you should be able to get the general
idea of what's going on here.
-- Seth
Henri Gomez wrote:
Do you have a patch against the current JNDIRealm ?
2008/4/22, Seth Leger <[EMAIL PROTECTED
Do you have a patch against the current JNDIRealm ?
2008/4/22, Seth Leger <[EMAIL PROTECTED]>:
> Henri Gomez wrote:
>
> > I do some search today and debugged TC 6.0.x trunk from my eclipse.
> > Authentification works great and the only remaining problem it so
> > setup roles in AD for users.
> >
>
Henri Gomez wrote:
I do some search today and debugged TC 6.0.x trunk from my eclipse.
Authentification works great and the only remaining problem it so
setup roles in AD for users.
I used :
ldap://ldap.mycorp.com:389";
alternateURL="ldap://ldap.mycorp.com:389";
connection
> It is possible to perform successful authentication against an Active
> Directory server with the standard JNDIRealm but only if:
>
> a) A bind DN and bind password is supplied to JNDIRealm
got that
> b) Anonymous searches (with null credentials) are successful against the
> server
>
> (b) i
It is possible to perform successful authentication against an Active
Directory server with the standard JNDIRealm but only if:
a) A bind DN and bind password is supplied to JNDIRealm
b) Anonymous searches (with null credentials) are successful against the
server
(b) is highly unlikely becaus
Did someone as a example LDAP configuration against AD available
against standard JNDIRealm ?
Regards.
2008/4/14, Seth Leger <[EMAIL PROTECTED]>:
> When working on this, I would appreciate if bug 44645 could also be
> resolved. It's a fairly trivial patch.
>
> https://issues.apache.org/bugzilla
When working on this, I would appreciate if bug 44645 could also be
resolved. It's a fairly trivial patch.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44645
I also have additional fixes for JNDIRealm that address problems in
connecting to Active Directory. The biggest issue is that duri
[EMAIL PROTECTED] wrote:
Brandon DuRette schrieb:
As I said in my mail (27 Feb 2008 to bug 42579) JNDIRealm is hardly
useable with (Windows Server 2003) Active Directory Domains --
except for very small / trivial cases.
After a long history of frustrations, I solved all the
Tomcat+AD-issues by
Brandon DuRette wrote:
1. I could not find a corresponding case in the bug database in either
the 5.5 or 6.0 builds. Since this is an issue in both, should I open it in
both? If not, does anyone care which one the issue is filed against?
No really, but if there is a choice 6.0
2.
Brandon DuRette schrieb:
> While trying to track down an issue with logins taking a very long time, I
> just discovered in the 5.5.26 source code/Javadoc for JNDIRealm (likewise in
> the 6.0 documentation) that there's a big bold TODO to support connection
> pooling in the JNDIRealm. I think this
xiaojing xu wrote:
>I think this bug is different from my problem.I want to use http digest
> mode
> (RFC2617 HTTP Authentication: Basic and Digest Access Authentication).
> And the bug 37984 just want to resolve password in MD5 digest(may be
> not use http digest mode).
Sorry - my bad. Too m
I think this bug is different from my problem.I want to use http digest mode
(RFC2617 HTTP Authentication: Basic and Digest Access Authentication).
And the bug 37984 just want to resolve password in MD5 digest(may be
not use http digest mode).
2007/9/17, Mark Thomas <[EMAIL PROTECTED]>:
> xiao
xiaojing xu wrote:
> Although I can change the getPassword function in JNDIRealm, I still
> want to know if tomcat can implement JNDIRealm
> in http digest mode without change code
No. See http://issues.apache.org/bugzilla/show_bug.cgi?id=37984
Mark
23 matches
Mail list logo
