GitHub user avallen reopened a pull request:

    https://github.com/apache/cxf-fediz/pull/4

    Fix wsclientWebapp by configuring client auth against STS

    17e8c07f37de0529b94b63199a92f4044f4aa3ff has changed the STS configuration 
so that it requires client cert authentication for its Transport port. 
    
    This port is also used by the wsclientWebapp sample for its "on-behalf-of" 
usecase. This pull request modifies the sample webapp so that it authenticates 
against the STS with a client cert for which it uses its SSL server 
certificate. The certificate is als added to the STS truststore . 
    
    The documentation of the necessary keystore modifications has been modified 
accordingly in the HowToGenerateKeysREADME.html.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/avallen/cxf-fediz 1.1.x-fix-wsclient-sample

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf-fediz/pull/4.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4
    
----
commit bf9fa7fa91b0c663fa628f05093c4daadad1543b
Author: Andreas Vallen <[email protected]>
Date:   2015-01-27T12:03:06Z

    Fix wsclientWebapp by configuring client auth against STS
    
    17e8c07f37de0529b94b63199a92f4044f4aa3ff has changed the STS configuration 
so that it requires client cert authentication for its Transport port. This 
port is also used by the wsclientWebapp sample for its "on-behalf-of" usecase. 
This modifies the sample webapp for supporting this new requirement. The 
documentation of the necessary keystore modifications has been modified 
accordingly in the HowToGenerateKeysREADME.html.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to