Article
Search
Shameless Plugs
Most Popular
Who's online
Online users
- Anonymous
- Anonymous
- Anonymous
User login
3125
Handling PKI.npm in Non-English Environments
Problem
When installing the latest PKI.npm (Nov 2006) and accessing the certificate pages in iManager 2.6 many pages display nothing but cryptic information on non-English browsers. The reason is that some localized message files are missing.
Solution
There are two workarounds until the updated message files are available for download:
a) Set your browser language to English and restart the browser. This approach will give you the original English messages, but it requires the English browser.
b) Open the "pki.npm" archive with a tool like WinZip, Jar, or UnZip. In the file you should find another file - "pki.jar" - which is another archive. In the pki.jar archive you will find the file "PKIResources_en.properties". Copy this file to your iManager server(s) into the path [your tomcat path]\webapps\nps\WEB-INF\classes and rename it to "PKIResources.properties". This approach will give you the original English PKI messages, independent of the browser setting.
You may even create your localized messages by copying the file with your locale (e.g., fr, de, es, pt, etc.) by saving a copy as "PKIResources_[your locale].properties" (e.g., "PKIResources_fr.properties") and translating it yourself.
Engineering is aware of the problem and will provide a solution with one of the next releases.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3125 reads
0