[jira] [Resolved] (CXF-4481) unable to generate WADL to java
[
https://issues.apache.org/jira/browse/CXF-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-4481.
---
Resolution: Fixed
Fix Version/s: 2.7.0
2.6.3
2.5.6
> unable to generate WADL to java
>
>
> Key: CXF-4481
> URL: https://issues.apache.org/jira/browse/CXF-4481
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, Tooling
> Environment: cxf version 2.6.1
> apache-maven-3.0.4
> java 1.7
>Reporter: yousef b
>Assignee: Sergey Beryozkin
> Fix For: 2.5.6, 2.6.3, 2.7.0
>
>
> i succeeded to created rest with CXF,all good except that i get error when
> generating WADL2java.
> i use the following configuration:
>
> org.apache.cxf
> cxf-wadl2java-plugin
> 2.6.1
>
>
> generate-sources
> generate-sources
>
>
> ${basedir}/target/generated/src/main/java
>
>
>
> http://localhost:8080/apache-cxf-rest-test?_wadl
> true
> true
>
> org.apache.cxf.systest.jaxrs.codegen.service
>
>
> http://superbooks=org.apache.cxf.systest.jaxrs.codegen.schema
>
>
>
>
>
> wadl2java
>
>
>
>
> stack error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project wad: Compilation failure: Compilation failure:
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,27]
> error: ';' expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,28]
> error: not a statement
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,30]
> error: ';' expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,31]
> error: illegal start of type
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,32]
> error: ';' expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResourceImpl.java:[11,41]
> error: expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResource.java:[18,20]
> error: = expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResource.java:[18,23]
> error: expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResource.java:[18,24]
> error: ';' expected
> [ERROR]
> \DEV\wad\target\generated\src\main\java\org\apache\cxf\systest\jaxrs\codegen\service\ServiceResource.java:[18,51]
> error: = expected
> wadl:
> http://wadl.dev.java.net/2009/02";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> attributeFormDefault="unqualified" elementFormDefault="unqualified">
>
>
>
>
>
>
>
>
>
>
>
>
>
> ref="user"/>
>
>
>
>
>
>
> base="http://127.0.0.1:8080/apache-cxf-rest-test/";> path="/service/"> type="xs:int"/> name="GET"> mediaType="application/xml"/> path="users"> mediaType="application/xml"/> path="users/bad"> mediaType="application/xml"/>
> please help
--
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
[jira] [Resolved] (CXF-4477) [WADL2JAVA] Generate incorrect primitive parameter type
[
https://issues.apache.org/jira/browse/CXF-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin resolved CXF-4477.
---
Resolution: Fixed
Fix Version/s: 2.7.0
2.6.3
2.5.6
> [WADL2JAVA] Generate incorrect primitive parameter type
>
>
> Key: CXF-4477
> URL: https://issues.apache.org/jira/browse/CXF-4477
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS, Tooling
>Affects Versions: 2.6.1
>Reporter: Hoan-Vu Phan
>Assignee: Sergey Beryozkin
>Priority: Critical
> Fix For: 2.5.6, 2.6.3, 2.7.0
>
>
> In org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator we have the code like
> this:
> XSD_SPECIFIC_TYPE_MAP = new HashMap();
> XSD_SPECIFIC_TYPE_MAP.put("string", "String");
> XSD_SPECIFIC_TYPE_MAP.put("decimal", "java.math.BigInteger");
> XSD_SPECIFIC_TYPE_MAP.put("integer", "long");
> If we have a wadl like this:
>
>
> it's always generate (String param1) and (String param2)
> So far as I know, xs:int and xs:long beside xs:string are the most usage type
> in WADL. But now it can not work any more
> I think this is a regression bug from
> **
> sergeyb 08.05.12 19:25:44
> [CXF-4292] Defaulting to String when WADL Generator can not determine a class
> name of the primitive type
> **
> For the solution, I think we can expand XSD_SPECIFIC_TYPE_MAP which the
> exactly mapping as a standard:
> http://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding
> Could you please have a look on this issue.
> Many many many thanks :)
--
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
[jira] [Created] (FEDIZ-20) IDP should maintain authentication state
Juan Manuel CABRERA created FEDIZ-20: Summary: IDP should maintain authentication state Key: FEDIZ-20 URL: https://issues.apache.org/jira/browse/FEDIZ-20 Project: CXF-Fediz Issue Type: New Feature Components: IDP Affects Versions: 1.0.0 Reporter: Juan Manuel CABRERA The IDP relies on the browser to cache the end user's credentials (classical way to work for a HTTP Basic authentication). So in the IDP there is no way to kill a end user session without killing the browser. The IDP should maintain these credentials (or better : the proof that these credentials were checked at some point - i.e. a token). If for instance this token is stored in the HTTP session, the IDP will then be capable of removing it from the session, effectively killing the authentication and forcing the end user to enter again his credentials. -- 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
[jira] [Updated] (FEDIZ-20) IDP should maintain authentication state
[ https://issues.apache.org/jira/browse/FEDIZ-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Manuel CABRERA updated FEDIZ-20: - Issue Type: Improvement (was: New Feature) > IDP should maintain authentication state > > > Key: FEDIZ-20 > URL: https://issues.apache.org/jira/browse/FEDIZ-20 > Project: CXF-Fediz > Issue Type: Improvement > Components: IDP >Affects Versions: 1.0.0 >Reporter: Juan Manuel CABRERA > > The IDP relies on the browser to cache the end user's credentials (classical > way to work for a HTTP Basic authentication). > So in the IDP there is no way to kill a end user session without killing the > browser. > The IDP should maintain these credentials (or better : the proof that these > credentials were checked at some point - i.e. a token). > If for instance this token is stored in the HTTP session, the IDP will then > be capable of removing it from the session, effectively killing the > authentication and forcing the end user to enter again his credentials. -- 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
[jira] [Created] (FEDIZ-21) Implement Identity federation with distinct IDPs for resource and requestor.
Juan Manuel CABRERA created FEDIZ-21: Summary: Implement Identity federation with distinct IDPs for resource and requestor. Key: FEDIZ-21 URL: https://issues.apache.org/jira/browse/FEDIZ-21 Project: CXF-Fediz Issue Type: Wish Reporter: Juan Manuel CABRERA Implement http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175018 -- 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
[jira] [Updated] (CXF-4484) Claims to SAML attribute encoding wrong
[ https://issues.apache.org/jira/browse/CXF-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated CXF-4484: -- Description: The ClaimsAttributeStatementProvider is responsible to transform the claims to a SAML attribute. SAML 1.1 provides an AttributeName and AttributeNamespace to name a SAML attribute. The AttributeName is a local name and the AttributeNamespace the namespace. Both values form a qualified name (uri). SAML 2.0 has only the Name attribute and a NameFormat whereas the latter says what kind of format the value is of the Name attribute like uri, basic, unspecified or custom. The current encoding in the ClaimsAttributeStatementProvider is not aligned with the above. SAML 2.0 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> de Issue: - If attibute is part of http://schemas.xmlsoap.org/ws/2005/05/identity/claims schema then the name of the SAML attribute is simple like "givenname" instead of fully qualified. - The NameFormat should not be http://schemas.xmlsoap.org/ws/2005/05/identity/claims. Proposal: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> de You can configure which NameFormat should be used like uri or unspecified (Microsoft uses unspecified, Shibboleth uri). Default stays for backwards compatibilty in 2.6 but would like to change the default to "unspecified" for 2.7. SAML 1.1 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims/language"; AttributeNamespace="http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> de Issue: - If attribute is not part of the http://schemas.xmlsoap.org/ws/2005/05/identity/claims the AttributeName is fully qualified (which it shouldn't) and the AttributeNamespace is again http://schemas.xmlsoap.org/ws/2005/05/identity/claims. Proposal: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims";> de was: The ClaimsAttributeStatementProvider is responsible to transform the claims to a SAML attribute. SAML 1.1 provides an AttributeName and AttributeNamespace to name a SAML attribute. The AttributeName is a local name and the AttributeNamespace the namespace. Both values form a qualified name (uri). SAML 2.0 has only the Name attribute and a NameFormat whereas the latter says what kind of format the value is of the Name attribute like uri, basic, unspecified or custom. The current encoding in the ClaimsAttributeStatementProvider is not aligned with the above. SAML 2.0 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> de Issue: - If attibute is part of http://schemas.xmlsoap.org/ws/2005/05/identity/claims schema then the name of the SAML attribute is simple like "givenname" instead of fully qualified. - The NameFormat should not be http://schemas.xmlsoap.org/ws/2005/05/identity/claims. Proposal: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> de You can configure which NameFormat should be used like uri or unspecified (Microsoft uses unspecified, Shibboleth uri). Default stays for backwards compatibilty in 2.6 but would like to change the default to "unspecified" for 2.7. SAML 1.1 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org
[jira] [Created] (CXF-4484) Claims to SAML attribute encoding wrong
Oliver Wulff created CXF-4484: - Summary: Claims to SAML attribute encoding wrong Key: CXF-4484 URL: https://issues.apache.org/jira/browse/CXF-4484 Project: CXF Issue Type: Bug Components: Services Affects Versions: 2.6.2 Reporter: Oliver Wulff The ClaimsAttributeStatementProvider is responsible to transform the claims to a SAML attribute. SAML 1.1 provides an AttributeName and AttributeNamespace to name a SAML attribute. The AttributeName is a local name and the AttributeNamespace the namespace. Both values form a qualified name (uri). SAML 2.0 has only the Name attribute and a NameFormat whereas the latter says what kind of format the value is of the Name attribute like uri, basic, unspecified or custom. The current encoding in the ClaimsAttributeStatementProvider is not aligned with the above. SAML 2.0 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> de Issue: - If attibute is part of http://schemas.xmlsoap.org/ws/2005/05/identity/claims schema then the name of the SAML attribute is simple like "givenname" instead of fully qualified. - The NameFormat should not be http://schemas.xmlsoap.org/ws/2005/05/identity/claims. Proposal: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> owu...@apache.org http://schemas.mycompany.com/claims/language"; NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> de You can configure which NameFormat should be used like uri or unspecified (Microsoft uses unspecified, Shibboleth uri). Default stays for backwards compatibilty in 2.6 but would like to change the default to "unspecified" for 2.7. SAML 1.1 Now: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> owu...@apache.org http://schemas.mycompany.com/claims/language"; AttributeNamespace="http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> de Issue: - If attribute is not part of the http://schemas.xmlsoap.org/ws/2005/05/identity/claims the AttributeName is fully qualified (which it shouldn't) and the AttributeNamespace is again http://schemas.xmlsoap.org/ws/2005/05/identity/claims. Proposal: http://schemas.xmlsoap.org/ws/2005/05/identity/claims";> oliver.wu...@zurich.ch http://schemas.mycompany.com/claims";> de -- 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
[jira] [Created] (FEDIZ-22) Improved support for other claims encoding in SAML attributes
Oliver Wulff created FEDIZ-22: - Summary: Improved support for other claims encoding in SAML attributes Key: FEDIZ-22 URL: https://issues.apache.org/jira/browse/FEDIZ-22 Project: CXF-Fediz Issue Type: Improvement Components: Plugin Affects Versions: 1.0.0 Reporter: Oliver Wulff Assignee: Oliver Wulff As described in CXF-4484 some fixes are required on the STS side to properly encode claims in SAML 1.1/2.0 attributes. This fix supports encoding prior to CXF-4484 and after. -- 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
[jira] [Created] (CXF-4485) Provide optional support for WADL resource parameters
Sergey Beryozkin created CXF-4485: - Summary: Provide optional support for WADL resource parameters Key: CXF-4485 URL: https://issues.apache.org/jira/browse/CXF-4485 Project: CXF Issue Type: Improvement Components: JAX-RS, Tooling Reporter: Sergey Beryozkin Assignee: Sergey Beryozkin Fix For: 2.5.6, 2.6.3, 2.7.0 At the moment resource-level parameters (path or matrix) are not inherited - this should be optionally supported -- 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
[jira] [Updated] (CXF-4485) Provide optional support for inheriting WADL resource parameters
[ https://issues.apache.org/jira/browse/CXF-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Beryozkin updated CXF-4485: -- Summary: Provide optional support for inheriting WADL resource parameters (was: Provide optional support for WADL resource parameters) > Provide optional support for inheriting WADL resource parameters > > > Key: CXF-4485 > URL: https://issues.apache.org/jira/browse/CXF-4485 > Project: CXF > Issue Type: Improvement > Components: JAX-RS, Tooling >Reporter: Sergey Beryozkin >Assignee: Sergey Beryozkin > Fix For: 2.5.6, 2.6.3, 2.7.0 > > > At the moment resource-level parameters (path or matrix) are not inherited - > this should be optionally supported -- 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
[jira] [Resolved] (FEDIZ-22) Improved support for other claims encoding in SAML attributes
[ https://issues.apache.org/jira/browse/FEDIZ-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff resolved FEDIZ-22. --- Resolution: Fixed Fix Version/s: 1.0.1 > Improved support for other claims encoding in SAML attributes > - > > Key: FEDIZ-22 > URL: https://issues.apache.org/jira/browse/FEDIZ-22 > Project: CXF-Fediz > Issue Type: Improvement > Components: Plugin >Affects Versions: 1.0.0 >Reporter: Oliver Wulff >Assignee: Oliver Wulff > Fix For: 1.0.1 > > > As described in CXF-4484 some fixes are required on the STS side to properly > encode claims in SAML 1.1/2.0 attributes. This fix supports encoding prior to > CXF-4484 and after. -- 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
[jira] [Commented] (FEDIZ-19) Single Sign Out
[ https://issues.apache.org/jira/browse/FEDIZ-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440649#comment-13440649 ] Oliver Wulff commented on FEDIZ-19: --- This issue depends on FEDIZ-20 > Single Sign Out > --- > > Key: FEDIZ-19 > URL: https://issues.apache.org/jira/browse/FEDIZ-19 > Project: CXF-Fediz > Issue Type: New Feature >Reporter: Romain Manni-Bucau > > The goal is to invalidate all sessions of "related" webapps with a single > action (button). -- 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
[jira] [Commented] (FEDIZ-21) Implement Identity federation with distinct IDPs for resource and requestor.
[ https://issues.apache.org/jira/browse/FEDIZ-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440654#comment-13440654 ] Oliver Wulff commented on FEDIZ-21: --- This request seems to be duplicate of FEDIZ-3. Do you agree? > Implement Identity federation with distinct IDPs for resource and requestor. > > > Key: FEDIZ-21 > URL: https://issues.apache.org/jira/browse/FEDIZ-21 > Project: CXF-Fediz > Issue Type: Wish >Reporter: Juan Manuel CABRERA > > Implement > http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175018 -- 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
[jira] [Updated] (FEDIZ-14) Make the TokenReplayCache implementation configurable in the Fediz configuration
[ https://issues.apache.org/jira/browse/FEDIZ-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-14: -- Component/s: Plugin Description: This task is to make the TokenReplayCache implementation configurable in the Fediz configuration. Currently the EhCacheTokenReplayCache implementation is used by default. (was: This task is to make the TokenReplayCache implementation configurable in the Fediz configuration. Currently the EhCacheTokenReplayCache implementation is used by default.) Affects Version/s: 1.0.0 > Make the TokenReplayCache implementation configurable in the Fediz > configuration > > > Key: FEDIZ-14 > URL: https://issues.apache.org/jira/browse/FEDIZ-14 > Project: CXF-Fediz > Issue Type: Improvement > Components: Plugin >Affects Versions: 1.0.0 >Reporter: Colm O hEigeartaigh > > This task is to make the TokenReplayCache implementation configurable in the > Fediz configuration. Currently the EhCacheTokenReplayCache implementation is > used by default. -- 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
[jira] [Updated] (FEDIZ-19) Single Sign Out
[ https://issues.apache.org/jira/browse/FEDIZ-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-19: -- Component/s: Plugin IDP > Single Sign Out > --- > > Key: FEDIZ-19 > URL: https://issues.apache.org/jira/browse/FEDIZ-19 > Project: CXF-Fediz > Issue Type: New Feature > Components: IDP, Plugin >Reporter: Romain Manni-Bucau > > The goal is to invalidate all sessions of "related" webapps with a single > action (button). -- 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
[jira] [Updated] (FEDIZ-21) Implement Identity federation with distinct IDPs for resource and requestor.
[ https://issues.apache.org/jira/browse/FEDIZ-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-21: -- Component/s: IDP > Implement Identity federation with distinct IDPs for resource and requestor. > > > Key: FEDIZ-21 > URL: https://issues.apache.org/jira/browse/FEDIZ-21 > Project: CXF-Fediz > Issue Type: Wish > Components: IDP >Reporter: Juan Manuel CABRERA > > Implement > http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175018 -- 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
[jira] [Updated] (FEDIZ-15) Support the publish of the WS-Federation Metadata document
[ https://issues.apache.org/jira/browse/FEDIZ-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-15: -- Component/s: IDP > 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 > Components: IDP >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
[jira] [Created] (FEDIZ-23) Support different authentication mechanism
Oliver Wulff created FEDIZ-23: - Summary: Support different authentication mechanism Key: FEDIZ-23 URL: https://issues.apache.org/jira/browse/FEDIZ-23 Project: CXF-Fediz Issue Type: Improvement Components: IDP Affects Versions: 1.0.0 Reporter: Oliver Wulff The IDP only supports basic authentication in the current setup. The IDP should introduce an interface to plugin a custom authentication mechanism. Per default, implementation for the following mechanism should be provided out of the box: - form based - certificate The authentication mechanism is chosen based on the wauth parameter passed in the signin request. If this parameter is missing the configured default is used. -- 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
[jira] [Commented] (FEDIZ-3) Support the role "Resource IDP" in IDP
[ https://issues.apache.org/jira/browse/FEDIZ-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440676#comment-13440676 ] Oliver Wulff commented on FEDIZ-3: -- Home realm discovery must be implemented. Initially, the Resource IDP processes the whr parameter of the signin request and redirects the browser to the requestor IDP. Later, the home realm discovery could be extended to support more sophisticated algorithms based on client parameters (HTTP headers, client idp, etc). The Resource IDP should maintain a session with the browser which doesn't enforce a redirect to the requestor idp if it has already been authenticated. Instead, he issues a new token for the RP directly. The exception is if the wauth parameter enforces a stronger authentication (certificate) than initially done like username/password. > Support the role "Resource IDP" in IDP > -- > > Key: FEDIZ-3 > URL: https://issues.apache.org/jira/browse/FEDIZ-3 > Project: CXF-Fediz > Issue Type: New Feature > Components: IDP >Reporter: Oliver Wulff > -- 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
[jira] [Created] (FEDIZ-24) maximumClockSkew is not optional
Oliver Wulff created FEDIZ-24: - Summary: maximumClockSkew is not optional Key: FEDIZ-24 URL: https://issues.apache.org/jira/browse/FEDIZ-24 Project: CXF-Fediz Issue Type: Improvement Components: Plugin Affects Versions: 1.0.0 Reporter: Oliver Wulff Assignee: Oliver Wulff Priority: Minor Fix For: 1.0.1 maximumClockSkew must be configured. Otherwise an exception occurs. maximumClockSkew should be optional where default is 5 seconds. -- 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
[jira] [Updated] (FEDIZ-24) maximumClockSkew is not optional
[ https://issues.apache.org/jira/browse/FEDIZ-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-24: -- Issue Type: Bug (was: Improvement) > maximumClockSkew is not optional > > > Key: FEDIZ-24 > URL: https://issues.apache.org/jira/browse/FEDIZ-24 > Project: CXF-Fediz > Issue Type: Bug > Components: Plugin >Affects Versions: 1.0.0 >Reporter: Oliver Wulff >Assignee: Oliver Wulff >Priority: Minor > Fix For: 1.0.1 > > > maximumClockSkew must be configured. Otherwise an exception occurs. > maximumClockSkew should be optional where default is 5 seconds. -- 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
[jira] [Resolved] (FEDIZ-24) maximumClockSkew is not optional
[ https://issues.apache.org/jira/browse/FEDIZ-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff resolved FEDIZ-24. --- Resolution: Fixed > maximumClockSkew is not optional > > > Key: FEDIZ-24 > URL: https://issues.apache.org/jira/browse/FEDIZ-24 > Project: CXF-Fediz > Issue Type: Bug > Components: Plugin >Affects Versions: 1.0.0 >Reporter: Oliver Wulff >Assignee: Oliver Wulff >Priority: Minor > Fix For: 1.0.1 > > > maximumClockSkew must be configured. Otherwise an exception occurs. > maximumClockSkew should be optional where default is 5 seconds. -- 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
