ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (WSS-360) Port BSP enforcer to streaming code.
Date Thu, 23 Aug 2012 14:44:42 GMT

    [ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439649#comment-13439649
] 

Colm O hEigeartaigh edited comment on WSS-360 at 8/24/12 1:43 AM:
------------------------------------------------------------------

Hi Marc,

I've moved the BSPRule stuff to the common module to make use of it for the DOM code as well.

I've noticed the following rules so far which are implemented by the DOM code that do not
appear to be implemented by the Stax code:

R3227("A SECURITY_HEADER MUST NOT contain more than one TIMESTAMP"),
R3033("Any X509_TOKEN MUST contain a ValueType attribute with a value of \"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3\""),
R5621("When used for Key Transport, any EK_ENCRYPTION_METHOD Algorithm attribute MUST have
a value of \"http://www.w3.org/2001/04/xmlenc#rsa-1_5\" or \"http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p\""),
 R3059("Any STR_REFERENCE MUST specify a ValueType attribute with the exception of STR_REFERENCE
pointing to a SAML_V2_0_TOKEN or a KERBEROS_TOKEN or an ENCRYPTED_KEY_TOKEN"),
    
R3058("Any STR_REFERENCE ValueType attribute MUST contain a value for the referenced SECURITY_TOKEN
specified by the corresponding security token profile"),
R5215("Any SECURITY_TOKEN_REFERENCE to a PKIPATH_TOKEN MUST contain a wsse11:TokenType attribute
with a value of \"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1\""),
R6603("Any STR_KEY_IDENTIFIER ValueType attribute that references a SAML_V1_1_TOKEN MUST have
a value of \"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID\""),
R6616("Any STR_KEY_IDENTIFIER ValueType attribute that references a SAML_V2_0_TOKEN MUST have
a value of \"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID\""),
R6604("Any STR_KEY_IDENTIFIER that references a SAML_TOKEN MUST NOT include an EncodingType
attribute"),
R6611("Any SECURITY_TOKEN_REFERENCE to a SAML_V1_1_TOKEN MUST contain a wsse11:TokenType attribute
with a value of \"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1\""),
R6617("Any SECURITY_TOKEN_REFERENCE to a SAML_V2_0_TOKEN MUST contain a wsse11:TokenType attribute
with a value of \"http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0\""),
R6614("Any SECURITY_TOKEN_REFERENCE that references an INTERNAL_SAML_V2_0_TOKEN using a STR_REFERENCE
MUST NOT contain a ValueType attribute"),
R4215("Any SECURITY_TOKEN_REFERENCE to a USERNAME_TOKEN MUST NOT contain an STR_KEY_IDENTIFIER"),
R4214("Any STR_REFERENCE to a USERNAME_TOKEN MUST have a ValueType attribute with a value
of \"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken\""),
    
Colm.

                
      was (Author: coheigea):
    Hi Marc,

I've moved the BSPRule stuff to the common module to make use of it for the DOM code as well.

I've noticed the following rules so far which are implemented by the DOM code that do not
appear to be implemented by the Stax code:

R3227("A SECURITY_HEADER MUST NOT contain more than one TIMESTAMP"),
R3033("Any X509_TOKEN MUST contain a ValueType attribute with a value of \"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3\""),
R5621("When used for Key Transport, any EK_ENCRYPTION_METHOD Algorithm attribute MUST have
a value of \"http://www.w3.org/2001/04/xmlenc#rsa-1_5\" or \"http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p\""),
    
Colm.

                  
> Port BSP enforcer to streaming code.
> ------------------------------------
>
>                 Key: WSS-360
>                 URL: https://issues.apache.org/jira/browse/WSS-360
>             Project: WSS4J
>          Issue Type: Sub-task
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0
>
>
> This task is to port the BSP enforcer used in the DOM code to the streaming code, to
enforce Basic Security Profile 1.1 requirements.

--
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message