November 2009 - jboss-identity-issues

[JBoss JIRA] Created: (JBID-211) jbid-handlers file is missing in three sample idp applications

by Marcel Kolsteren (JIRA)

jbid-handlers file is missing in three sample idp applications -------------------------------------------------------------- Key: JBID-211 URL: https://jira.jboss.org/jira/browse/JBID-211 Project: JBoss Identity Issue Type: Bug Reporter: Marcel Kolsteren Assignee: Anil Saldhana In the sample applications idp, idp-sig and idp-sig-no-val applications, there is no jbid-handlers file. This leads to "InputStream is null" errors when starting one of those idp 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBID-217) STSSecurityHandler: Improve exception/fault handling.

by Daniel Bevenius (JIRA)

STSSecurityHandler: Improve exception/fault handling. ----------------------------------------------------- Key: JBID-217 URL: https://jira.jboss.org/jira/browse/JBID-217 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Improve the exception handling in this class. Currently only a WebServiceException is thrown from the handleMessage method. Use the appropriate fault codes that are defined in WS-Security for handling execptions in this handler: UnsupportedSecurityToken InvalidSecurity InvalidSecurityToken FailedAuthentication FailedCheck SecurityTokenUnavailable -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-224) sample application idp-sig-no-val doesn't return the relay state to the SP

by Marcel Kolsteren (JIRA)

sample application idp-sig-no-val doesn't return the relay state to the SP -------------------------------------------------------------------------- Key: JBID-224 URL: https://jira.jboss.org/jira/browse/JBID-224 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation Affects Versions: IDENTITY-1.0.0.CR1 Reporter: Marcel Kolsteren Assignee: Anil Saldhana The sample IDP idp-sig-no-val doesn't return the relayState to the SP. This is caused by the handleRequestType(...) method of SAML2AuthenticationHandler, that fails to copy the relayState from request to response. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBID-110) IDM API review - returned values and Exceptions

by Boleslaw Dawidowicz (JIRA)

IDM API review - returned values and Exceptions ----------------------------------------------- Key: JBID-110 URL: https://jira.jboss.org/jira/browse/JBID-110 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.beta2 Every "find" type method in IDM API should be reviewed to follow proper behaviour. Either null object should be returned or method should throw meaningful exception. For example: - User findUser() throws IdentityException. The best is to have simply null returned when search fail. Other acceptable option is to expect exact exception like "UserNotFoundException". It is not acceptable to receive "IdentityException" when user is simply not found in identity store. General exception like IdentityException should be reserved for system failures or more serious runtime issues. All other methods should have similar behaviour. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBID-105) getAttributeDescription()/getSupportedAttributesDescriptions() for types

by Boleslaw Dawidowicz (JIRA)

getAttributeDescription()/getSupportedAttributesDescriptions() for types ------------------------------------------------------------------------ Key: JBID-105 URL: https://jira.jboss.org/jira/browse/JBID-105 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Anil Saldhana Fix For: 1.0.0.CR2 missing in AttributesManager: AttributeDescription getUserAttributeDescription(String name); AttributeDescription getGroupTypeAttributeDescription(String groupTypeName, String name); Map<String, AttributeDescription> getUserSupportedAttributesDescriptions(); Map<String, AttributeDescription> getGroupTypeSupportedAttributesDescriptions(String groupTypeName); -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBID-103) Improve logging

by Boleslaw Dawidowicz (JIRA)

Improve logging --------------- Key: JBID-103 URL: https://jira.jboss.org/jira/browse/JBID-103 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: idm-1.0.0.GA Add more debug level logging in all important components. It needs to be decided which logging framework to use. JUL has major downside because JBoss AS needs to be tweaked to use logging.properties. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBID-226) Release Picketlink 1.0.0.GA

by Stefan Guilhen (JIRA)

Release Picketlink 1.0.0.GA --------------------------- Key: JBID-226 URL: https://jira.jboss.org/jira/browse/JBID-226 Project: JBoss Identity Issue Type: Release Components: Identity-Federation Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDENTITY-1.0.0.CR1 Release Picketlink 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBID-225) double question mark in URL when redirecting to Google IDP

by Marcel Kolsteren (JIRA)

double question mark in URL when redirecting to Google IDP ---------------------------------------------------------- Key: JBID-225 URL: https://jira.jboss.org/jira/browse/JBID-225 Project: JBoss Identity Issue Type: Bug Reporter: Marcel Kolsteren Assignee: Anil Saldhana The Google interop testing IDP uses the following URL for the single sign on service (HTTP_Redirect binding): https://www.google.com/accounts/o8/saml/meta?hd=lso-test-domain.com When a JBoss Identity based SP builds the URL to which the authentication request is sent, it just adds "?SAMLRequest=..." to the URL of the single sign on service, which leads to a double question mark in the final URL to which the browser is redirected. I already fixed this problem in the Seam authentication filter, but it still needs to be solved at other places where the redirect binding is used: - IDPWebRequestUtil - SPRedirectFormAuthenticator - SPRedirectSignatureFormAuthenticator -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBID-104) attribute/credential data size limit

by Boleslaw Dawidowicz (JIRA)

attribute/credential data size limit ------------------------------------ Key: JBID-104 URL: https://jira.jboss.org/jira/browse/JBID-104 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.beta2 There should be configuration option that limits acceptable data size for attributes and credentials. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBID-223) sample application idp-sig-no-val signs twice

by Marcel Kolsteren (JIRA)

sample application idp-sig-no-val signs twice --------------------------------------------- Key: JBID-223 URL: https://jira.jboss.org/jira/browse/JBID-223 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation Reporter: Marcel Kolsteren Assignee: Anil Saldhana Fix For: IDENTITY-1.0.0.CR1 In the sample application idp-sig-no-val, the outgoing messages are signed twice. This is caused by the fact that picketlink-handlers.xml still contains the obsolete SAML2SignatureGenerationHandler. The IDP sample applications employee-sig and sales-sig probably suffer from the same problem. -- 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, 1 month

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues November 2009