[
https://issues.apache.org/jira/browse/FEDIZ-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906763#comment-13906763
]
Oliver Wulff commented on FEDIZ-71:
-----------------------------------
A check must be added in STSPortFilter whether port is configured to 0, then
update the port with current port otherwise ignore as the STS is running
externally.
> Enable use of Apache CXF Fediz IDP with external third-party WS-Trust STS
> -------------------------------------------------------------------------
>
> Key: FEDIZ-71
> URL: https://issues.apache.org/jira/browse/FEDIZ-71
> Project: CXF-Fediz
> Issue Type: Improvement
> Components: IDP
> Affects Versions: 1.1.0
> Environment: External WS-Trust 1.0 STS based on Oracle Metro
> framework.
> Reporter: Stepan Hrbacek
> Assignee: Colm O hEigeartaigh
> Fix For: 1.1.1
>
> Attachments: fediz-1.1.0.services.idp.patch
>
>
> We have tried to use Apache CXF Fediz IDP 1.1.0 with our WS-Trust 1.0 STS
> running on a different machine from the IDP based on the Oracle Metro
> framework and have experienced following issues:
> - WS-Trust version cannot be configured in the Fediz IDP.
> - The STS port used by the Fediz IDP is always the one used by the IDP.
> After patching 3 Fediz IDP classes (STSAuthenticationProvider.java,
> STSClientAction.java, STSPortFilter.java) we have partially succeeded (failed
> on an issue in our STS). We would appreciate very much, if the Fediz IDP
> enables to configure the WS-Trust and WS-Addressing namespaces.
> Please find a patch of the affected classes attached.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
