SIMP: CIM_Account/RequestStateChange Mehtod is not supported

Status: Beta

Brought to you by: akash_malhotra, christiankrause, georghoesch, michaelbaumann, and 2 others

#56 SIMP: CIM_Account/RequestStateChange Mehtod is not supported

Milestone: v1.0.3

Status: open-fixed

Owner: Thomas Weber

Labels: DASH Reference Implementation (66)

Priority: 6

Updated: 2008-03-18

Created: 2008-03-03

Creator: Akash_Malhotra

Private: No

According to DSP1034 section 8.2.1 if RequestedSTateSUpported property has one value then RequestSTateCHange method shall be supported

WHen OTM execute RequestStateCHange method, target responds with wsa:ActionNotSupported

Discussion

Akash_Malhotra - 2008-03-03

labels: --> DASH Reference Implementation

assigned_to: nobody --> tweb
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-03-04

Logged In: YES
user_id=2002123
Originator: NO

Please select the relevant RI version using the Group field (eg. v1.0.2 or v1.0.3).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-03-04

Logged In: YES
user_id=2002123
Originator: NO

Please state the RI version using the Group field (eg. v1.0.1 or v1.0.3)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Akash_Malhotra - 2008-03-04

Logged In: YES
user_id=1720313
Originator: YES

its difficult for OTM for put revison numner since we used latest drop from FTP site. In future OTM team will supply DASH RI DTP revison number

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-03-04

Logged In: YES
user_id=2002123
Originator: NO

I understand and agree that we should use DTP revision number. And the developers can also use this DTP revision number to specify the build into which the fix was put in.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Weber - 2008-03-18

milestone: --> v1.0.3

priority: 5 --> 6
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Weber - 2008-03-18

Logged In: YES
user_id=1857294
Originator: NO

RequestStateChange is not supported for RI 1.0.3, need to adapt RequestedStatesSupported in emulation.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Weber - 2008-03-18

Logged In: YES
user_id=1857294
Originator: NO

Fixed and await to be released in RI 1.0.4.
Fixes Profiles/SimpleIdentityManagement/CIM_Account failure.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Weber - 2008-03-18

status: open --> open-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-03-18

Logged In: YES
user_id=2002123
Originator: NO

This fix will be verified when testing the v1.0.4 release.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-03-25

Logged In: YES
user_id=2002123
Originator: NO

The test does not fail anymore but the target reports a "method not implemented" error. According to the extrinsic method list provided, this method is a supported method. I need clarification on this issue.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Thomas Weber - 2008-03-26

Logged In: YES
user_id=1857294
Originator: NO

I'm sorry about the confusion. As for role based authentication, for the simple identity management profile we also implemented the RequestStateChange extrinsic method. However the current implementation does only support static accounts. This is expressed by an empty set of RequestedStatesSupported in the according capabilities property which causes OTM to report
INFO:The Method RequestStateChange() is not implemented at the target

Returning empty arrays is a known problem of WS Man. Property arrays usually are expressed as a sequence of properties with the same name. An empty array thus is a series of zero properties and cannot be distinguished from a property not existant. Mandatory properties which can be emtpy arrays are a real problem.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-04-03

Logged In: YES
user_id=2002123
Originator: NO

Akash, can you please comment on the explanation that Thomas provided below? I need to understand if this is still an issue with respect to RI?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Navin Boppuri - 2008-04-04

Logged In: YES
user_id=2002123
Originator: NO

Akash: Fixed

Will verify it on OTM 1.0.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.