You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2008/01/28 14:25:36 UTC
[jira] Created: (RAMPARTC-60) When encryption token assertion and
signature token assertion is given in symmetric binding, two session keys
have to be created.
When encryption token assertion and signature token assertion is given in symmetric binding, two session keys have to be created.
---------------------------------------------------------------------------------------------------------------------------------
Key: RAMPARTC-60
URL: https://issues.apache.org/jira/browse/RAMPARTC-60
Project: Rampart/C
Issue Type: Bug
Components: Rampart-core
Affects Versions: 1.1.0
Environment: N/A
Reporter: S.Uthaiyashankar
Assignee: S.Uthaiyashankar
Priority: Trivial
Fix For: 1.2.0
When Protection token assertion is given, one session key is used for encryption and signature. But when Encryption token assertion and signature token assertion is given instead of protection token assertion, then two session keys should be used.
This can be implemented using key arrays (currently used by derived keys) to store the session keys with the key name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (RAMPARTC-60) When encryption token assertion and
signature token assertion is given in symmetric binding, two session keys
have to be created.
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar resolved RAMPARTC-60.
--------------------------------------
Resolution: Fixed
this is done. When ProtectionToken assertion is given, then one session key is used. If SignatureToken + EncryptionToken assertion is given, two session keys are used.
> When encryption token assertion and signature token assertion is given in symmetric binding, two session keys have to be created.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPARTC-60
> URL: https://issues.apache.org/jira/browse/RAMPARTC-60
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.1.0
> Environment: N/A
> Reporter: S.Uthaiyashankar
> Assignee: S.Uthaiyashankar
> Priority: Trivial
> Fix For: 1.2.0
>
>
> When Protection token assertion is given, one session key is used for encryption and signature. But when Encryption token assertion and signature token assertion is given instead of protection token assertion, then two session keys should be used.
> This can be implemented using key arrays (currently used by derived keys) to store the session keys with the key name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (RAMPARTC-60) When encryption token assertion and
signature token assertion is given in symmetric binding, two session keys
have to be created.
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar closed RAMPARTC-60.
------------------------------------
> When encryption token assertion and signature token assertion is given in symmetric binding, two session keys have to be created.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPARTC-60
> URL: https://issues.apache.org/jira/browse/RAMPARTC-60
> Project: Rampart/C
> Issue Type: Bug
> Components: Rampart-core
> Affects Versions: 1.1.0
> Environment: N/A
> Reporter: S.Uthaiyashankar
> Assignee: S.Uthaiyashankar
> Priority: Trivial
> Fix For: 1.2.0
>
>
> When Protection token assertion is given, one session key is used for encryption and signature. But when Encryption token assertion and signature token assertion is given instead of protection token assertion, then two session keys should be used.
> This can be implemented using key arrays (currently used by derived keys) to store the session keys with the key name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.