Closed GoogleCodeExporter closed 8 years ago
Can you try commenting line 447 in NMASCrOperator.java:
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
Original comment by jrivard
on 28 Aug 2013 at 2:37
Thanks, that seems to fix the issue. However I notice that the the NMAS login
spits out uncontrolled logging:
2013-08-28 20:59:10, TRACE, cr.NMASCrOperator, starting NMASSessionMonitor
thread id=2 activeCount=2
<<open session> >> reply (NMAS ID) 262273
2013-08-28 20:59:10, DEBUG, operations.CrService, {4} returning responses read
via method NMAS for user cn=testuser,ou=users,o=meta [123.456.789.14]
Should I consider this as a feature from the NMAS libraries or should I file a
seperate issue for this?
Original comment by sebastia...@gmail.com
on 28 Aug 2013 at 7:08
It's a feature. Not much I can do about it :( Change checked into revision
604.
Original comment by jrivard
on 28 Aug 2013 at 7:11
Thanks! I'll do some further testing with this new functionality. Especially
the number of open NMAS Session threads need some extensive testing. Unless I'm
mistaken, the NMAS timeout is hardcoded to 3 minutes. A couple of quick tests
do not show a cleanup of those inactive threads (User presses cancel button
after getting the Challenge presented via NMAS). This might be another (new)
issue.
Original comment by sebastia...@gmail.com
on 28 Aug 2013 at 7:33
Original issue reported on code.google.com by
sebastia...@gmail.com
on 28 Aug 2013 at 2:14