Task #3630
Task #3629: Handle CILogon DN containing UTF-7 encoded special characters
Configure CN to handle UTF-7
0%
Description
In order to get UTF-7 support using the CharactersetProvider, I needed to add to the JRE extension or else Tomcat would not pick this up for the webapp[s]
sudo cp /var/lib/tomcat6/webapps/portal/WEB-INF/lib/jutf7-1.0.0.jar /usr/lib/jvm/java-6-sun/jre/lib/ext/
This should be added to the buildout. Perhaps cn-os-core, since it will be required for anything that needs to decode the DN from the client certificate (basically everything).
History
#1 Updated by Ben Leinfelder over 11 years ago
Some background information that led to the jre/ext solution:
http://docs.oracle.com/javase/6/docs/api/java/nio/charset/spi/CharsetProvider.html
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4619777
http://stackoverflow.com/questions/6308587/loading-a-java-charset-manually
#2 Updated by Robert Waltz over 11 years ago
This will re-inforce the problem with our installation procedures that we wish to solve by eliminating bouncycastle jars/security modifications in the jre.
Anytime we update java independent of one of our debian (dataone-cn-os-core or something) installation packages, we have to fix things by hand in java.
#3 Updated by Ben Leinfelder over 11 years ago
- Status changed from New to Rejected
- translation missing: en.field_remaining_hours set to 0.0
We will not decode the UTF-7 sequences after all. I backed out the jre lib/ext change on cn-dev.
