[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issues identified in the core and some profiles
Dear all, While going again through the core and some profiles I have hit some issues, for which I would ask some kind of resolution. I might identify more issues in the forecoming days as I am reviewing certain aspects of the core and some profiles. By the way, I have been looking to the Issues section of our Kavi....but not find out how to create a new issue....Stefan, could you let me know how to do it? Once I know it I will create these issues in the Kavi and so record them Regards Juan Carlos. LIST OF ISSUES
In DSS core 1.0 the type saml:NameIdentifierType is used; this is a type defined in SAML 1.0. SAML 2.0 has substituted this type with NameIDType. I propose that version 2.0 of the core uses this type. 2. RequestTransformedDocument.
DSS Core 1.0.
DSS Core 1.0. There should be some mechanism for passing constraints to the server. Should this appear into the core?
B. Multi-signature verification report. The profile defines three different levels of details...could
there be more? C. ASYNCHRONOUS PROCESSING PROFILE 1. PendingRequest
This profile allows OptionalInputs?. Text says: " Any additional
inputs to the request. This element may be used e.g. for
authentication data"
I am not sure that in any of the optional inputs in the core there
is an OptionalInput? for conveying authentication
data. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]