August 2009 - jboss-identity-issues

[JBoss JIRA] Created: (JBID-116) Liberty ID-WSF webapp to serve the wsdl

by Anil Saldhana (JIRA)

Liberty ID-WSF webapp to serve the wsdl --------------------------------------- Key: JBID-116 URL: https://jira.jboss.org/jira/browse/JBID-116 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-168) improve and extend the sample SAMLv2 IDP and SP applications

by Marcel Kolsteren (JIRA)

improve and extend the sample SAMLv2 IDP and SP applications ------------------------------------------------------------ Key: JBID-168 URL: https://jira.jboss.org/jira/browse/JBID-168 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha5 Reporter: Marcel Kolsteren Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 Currently we have five SAMLv2 IDP/SP sample applications, working together in a Tomcat environment: - idp.war - idp-sig.war - employee.war - sales.war - sales-post-sig.war For a JBoss AS 5 environment and for a Seam SP, we don't have examples yet that work "out of the box". Therefore the proposal is to create a fed-example.ear, that contains these two war files that form an IDP-SP pair: - idp-sig.war (the same that is used for Tomcat) - seam-sp.war This ear will be created. In addition, the following improvements will be made for the existing valve-based IDP and SP apps: - split /resources into /src/main/resources and /src/main/webapps, according to the Maven standard locations; most files will be in webapps, only the keystore remains in resources - add the roles Employee and Sales to the idp applications (currently only manager is mentioned in web.xml, while the Employee and Sales roles are needed in order to get access to the employee and sales applications) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-167) automatic application server detection

by Marcel Kolsteren (JIRA)

automatic application server detection -------------------------------------- Key: JBID-167 URL: https://jira.jboss.org/jira/browse/JBID-167 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha5 Reporter: Marcel Kolsteren Assignee: Anil Saldhana Currently the Service Provider configuration file contains a ServerEnvironment attribute, which is either tomcat or JBOSS. <JBossSP xmlns="urn:jboss:identity-federation:config:1.0" ServerEnvironment="tomcat"> ... </JBossSP> It would be more convenient if JBID could "sense" in which application server environment it is running. Then an application can be deployed in different containers without having to change the configuration file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBID-126) IDPWebBrowserSSOValve needs work to send the error response properly

by Anil Saldhana (JIRA)

IDPWebBrowserSSOValve needs work to send the error response properly --------------------------------------------------------------------- Key: JBID-126 URL: https://jira.jboss.org/jira/browse/JBID-126 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 When there are exceptions such as IssuerNoTrustedException, the IDP should send a proper saml response. For this, the valve needs to preprocess the saml request and determine the assertion consumer url. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-165) Cache JAXBContext rather than create each time

by Anil Saldhana (JIRA)

Cache JAXBContext rather than create each time ---------------------------------------------- Key: JBID-165 URL: https://jira.jboss.org/jira/browse/JBID-165 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: IDENTITY-1.0.0.alpha5 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta2 JAXBContext.newInstance is a very costly process. It should be possible to cache. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBID-147) XML Signature CanonicalizationMethod should be EXCLUSIVE_WITH_COMMENTS

by Anil Saldhana (JIRA)

XML Signature CanonicalizationMethod should be EXCLUSIVE_WITH_COMMENTS ---------------------------------------------------------------------- Key: JBID-147 URL: https://jira.jboss.org/jira/browse/JBID-147 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha4 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 Some details are at http://forums.sun.com/thread.jspa?threadID=5198619&start=15&tstart=0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-118) SAML2: HTTP/Post profile : Sign Assertions

by Anil Saldhana (JIRA)

SAML2: HTTP/Post profile : Sign Assertions ------------------------------------------ Key: JBID-118 URL: https://jira.jboss.org/jira/browse/JBID-118 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-164) SAML parsing/marshalling needs to use DOM

by Anil Saldhana (JIRA)

SAML parsing/marshalling needs to use DOM ----------------------------------------- Key: JBID-164 URL: https://jira.jboss.org/jira/browse/JBID-164 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha5 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 SInce JAXB is not friendly to XML Signatures, it is necessary to use DOM directly for parsing and marshalling. We can use JAXB as a read only view of the DOM to deal with Java objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-166) Create a single cached JAXBContext for the object models

by Anil Saldhana (JIRA)

Create a single cached JAXBContext for the object models -------------------------------------------------------- Key: JBID-166 URL: https://jira.jboss.org/jira/browse/JBID-166 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBID-163) fill ProtocolBinding attribute of AuthnRequest messages

by Marcel Kolsteren (JIRA)

fill ProtocolBinding attribute of AuthnRequest messages ------------------------------------------------------- Key: JBID-163 URL: https://jira.jboss.org/jira/browse/JBID-163 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha5 Reporter: Marcel Kolsteren Assignee: Anil Saldhana According to the SAMLv2 specification, the attributes AssertionConsumerServiceURL and ProtocolBinding (both optional) typically accompany each other. I found that AuthnRequest messages sent by JBID to an OpenSSO IDP are rejected, because the AssertionConsumerServiceURL is filled, but the ProtocolBinding is left blank. My proposal is to change the JBossSAMLAuthnRequestFactory so that it fills ProtocolBinding with HTTP-POST. As far as I know, the other possible binding for the assertion consumer, HTTP-Artifact, is not supported by JBID. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues August 2009