[
https://issues.apache.org/jira/browse/FEDIZ-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294245#comment-13294245
]
Alex Sarafian commented on FEDIZ-15:
------------------------------------
On the WIF/ADFS world there are two kinds of automation for the configuration
of both passive and active profiles.
First FedUtil is used to consume the Metadata of the STS (ADFS) from a url like
this https://sts_host/federationmetadata/2007-06/federationmetadata.xml. The
result of this action is a web.config file properly modified to consume the sts
and a FederationMetadata.xml that can be used from the STS to configure the
Relying Party as a second step.
It is my understanding that the first step (FederationMetadata.xml export from
the STS) is not yet supported but consuming a Service provider's
FederationMetadata.xml to configure the STS is.
If I am correct then yes I'm referring to the IDP/STS to export the
WS-Federation Metadata documents.
> Support the publish of the WS-Federation Metadata document
> ----------------------------------------------------------
>
> Key: FEDIZ-15
> URL: https://issues.apache.org/jira/browse/FEDIZ-15
> Project: CXF-Fediz
> Issue Type: Wish
> Reporter: Alex Sarafian
>
> It would be really good if Fediz supporter WS-Federation Metadata documents
> like ADFS does.
> It is really helpful for the .NET stack using the Windows Identity Foundation
> Federation Utility (FedUtil) for configuration of the WIF stack for Passive
> and Active profiles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
