A few weeks ago, I discussed an issue where a profile could no longer be created on WebSphere Application Server 220.127.116.11. It boiled down to an issue with the Java security policy files and thier ‘restricted’ and ‘unrestricted’ flavours. At the time, I thought that WebSphere actually required the unrestricted versions.
To test my theory I created my own 18.104.22.168 server and created a profile. It worked just fine without installing the unrestricted policy files. This means that my issue is that my environment is actually telling WebSphere (some-how) to use encryption algorithims used in the unrestricted jar. I’m still trying to figure out what part of my environment setup is doing this, but I thought it would be a service to the internet to document where I’m at currently.