Support for wauth and whr is supported as a callbackhandler in the fediz plugin for the relying party (application). Also metadata support is provided in the plugin. It's not yet supported for the fediz idp.
------ Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com ________________________________________ From: Cabrera Juan Manuel [juan-manuel.cabr...@atos.net] Sent: 04 September 2012 16:47 To: dev@cxf.apache.org Subject: RE: Facing error on Weblogic 11g with Apache CXF |u sing POST IN REST |Need help Hello everyone. I just dug out an old email about the Fediz roadmap (March, 29th 2012): http://mail-archives.apache.org/mod_mbox/cxf-dev/201203.mbox/%3c79ab4452999c844d9920e03635332731120...@s10be002.sh10.lan%3E#archives >> Roadmap >> ------------- >> >> 1st release (end of april): >> - Move configuration code to fediz-core >> - Publish WS-Federation Metadata document >> - Move SignIn request creation to fediz-core >> - support callback handlers for federation parameters: wauth, whr, >> >> 2nd release (end of june): >> - Create CXF plugin for JAX-RS >> - Create Websphere plugin based on TAI >> - Support encrypted token >> - Support the role of relying party IDP in mock >> - Support SAML HoK: >> either use UseKey element in RST >> or collocate STS in IDP thus STS has access to underlying transport >> - add layer to support other protocols like SAML-P, OAuth >> >> 3rd release (end of september): >> - create JBoss plugin >> - create Jetty plugin Just to know if it is still correct (excepting the dates, obviously); I am very interested in the features about federation (wauth, whr, metadata, ...) Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
