On Wed, Nov 30, 2011 at 5:11 PM, Stadelmann Josef < josef.stadelm...@axa-winterthur.ch> wrote:
> Hi Prabath**** > > ** ** > > Thanks for taking the ball and asking me about my issues; well I have > some….**** > > ** ** > > *I believe you, that your WCF-AXIS2 interop-tests run fine. * > > ** ** > > The issue I have with that is that such test are poorly if ever documented. > **** > > No setups, no examples are given, at least I did not find any so far; > maybe my overlook. **** > > Any links welcome, best to places where it is explained how to redo it our > self and learn!**** > > It would really convince us in the field. J**** > > ** ** > > AND**** > > ** ** > > among that, I feel a bit lost if certain questions are not answered. **** > > I.e. **** > > "is it possible to only encrypt a single xml element in the message body" > using Rampart?**** > > either my question was not clear, even simple, or maybe too simple. At > least I still don’t know it.**** > > ** ** > > Among that, where can I find a map how Rampart Security Policy elements > are mapped **** > > to WCF app.config or WCF custom binding elements and there further down > into underlying binding objects to attribute/values?.**** > > ** ** > > ** ** > > There are so many configuration setups possible on either side, **** > > WCF 3.5 (4.0) .NET and AXIS2/RAMAPRT that seldom all possible > configurations are tested.**** > > ** ** > > **** > > That is fostered by articles and relevant entries and blogs of i.e.**** > > Dennis Sosnoski (in this forum under Re: Securing SOAP Messages with > Rampart subject).**** > > ** ** > > ** ** > > but among that:**** > > ** ** > > The most recent example: I just finished all sample of Rampart except the > tomcat ut-over-https. **** > > The reason is: It is said in this samples README that I have to just > follow a few simple steps. **** > > But doing it did just not make my Tomcat 6.0.26 on Windows Vista turning > on the https 8443 port. **** > > Delivering the rampart-samples-key.jks and adding **** > > ** ** > > ** ** > > <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"**** > > maxHttpHeaderSize="8192"**** > > maxThreads="150" scheme="https" secure="true"**** > > clientAuth="false" sslProtocol="TLS"**** > > truststoreFile="rampart-sample-keys.jks"**** > > truststorePass="apache"**** > > truststoreType="JKS"**** > > keystoreFile="rampart-sample-keys.jks"**** > > keystorePass="apache" />**** > > ** ** > > in server.xml did not turn on that port? **** > > WHY – I can't say that – at least it seems to be not so simple. > Did you get an error after that HTTPS connector was added? If so, please send the stacktrace. We do add connectors that way all the time, and it always works. Perhaps your keystore is corrupted or the keystore password is incorrect. Can you generate your own JKS file & retry? > ** ** > > *Step7: Start tomcat. View > https://127.0.0.1:8443/axis2/services/listServices to see whether the > service is available.* > > is still a no go too, and I can't say why? Even after adding to server.xml > as shown below.**** > > * * > > the built service is deployed very successful > Can you attach the service you built? Did you see any exceptions while the service was being deployed? Please attach all stacktraces. It seems like something is seriously wrong at your end because not even the simplest thing is working.
