nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CreateMember fails with fault message "Member type must be user or group"

Bohdan_Hanchuk

Submitting CreateMember operation request keeps failing with
"a:MemberService.MemberTypeUserOrGroupRequired" fault code and "Member type must be user or group" fault string.

The Type propery is being provided, using both "Group" and "User". Is this a bug? Any thoughts on whats wrong? What to try?

Copy of SOAP request

      <urn1:CreateMember xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <urn1:member>
            <urn1:Type>Group</urn1:Type>
            <urn1:CreatedBy>1000</urn1:CreatedBy>
            <urn1:Deleted>false</urn1:Deleted>
            <urn1:Name>tester</urn1:Name>
         </urn1:member>
      </urn1:CreateMember>

Thanks

Find more posts tagged with

Comments

Appu_Nair1

See this e.g by Kyle https://knowledge.opentext.com/knowledge/cs.dll/Properties/17485166

In that code he does a constructor,when he wants a user he uses user ,whenhe wants a group he does group

Perhaps that would get you thinking about the SOAP envelope correctly.There are also several threads in which

Jason Smith/Scott Grasley talks about subtle differences between .NET,Java nd SOAP in general

// 8) Create new users
            //====================================================================================
            MemberService.User[] newUsers = {new MemberService.User(), new MemberService.User(), new MemberService.User()};

// NOTE: Although the prototype for the CreateMember call takes a second parameter of type
                //       MemberService.Member, one should be passing in either a MemberService.User or
                //       MemberService.Group, depending on which type of member you wish to create.

Bohdan_Hanchuk

HI Appu,

I took a look a the code, and there is a CreateMember method, to create group, but there wasn't enough info on what the value for "Type" should be. Actually from what I could tell Type was not being set any where in the code. I did read note about passing MemberService.Group instead of MemberService.Member put is doesn't appply to me as I'm using SoapUI instead of C# or Java.

I have been using SoapUI to build the SOAP package directly/manually based on the WSDL and associated XML Schemas. I've been successful to date with quite a few other methods/operations. I suspect I may be missing something ... simple ... for CreateMember method as I keep getting the same SOAP fault "MemberService.MemberTypeUserOrGroupRequired" with fault string "Member type must be user or group", even though I've tried different combinations of elements, passing "Group" for the Type element each time. I've looked thorugh the API documentation but there wasn't enough info there either.

I suppose I can do some reverse engineereing by setting up a C# project, then build and submit the CreateMember method and inspect the SOAP package it builds/sends with WireShark to see what is missing ... but I hoping there is/was a simpler way.

Thanks

Appu_Nair1

I ran this snippet of Kyle code exactly this

          MemberService.User[] newUsers = { new MemberService.User() };
            MemberService.Member newSingleUserResult;

            try
            {
                // Required Fields
                newUsers[0].Name = "newuser0";
                newUsers[0].Password = "mypassword";
                newUsers[0].DepartmentGroupID = 1001;
                newSingleUserResult = ms.CreateMember(ref msOTAuth, newUsers[0]);
            }
            catch (Exception e)
            {
                Console.WriteLine("Error: " + e.Message);
                ms.Close();
                return;
            }

I then put Fiddler before I submitted my request

When I submitted Fiddler showed this

POST http://changedforposting/les-sso/MemberService.svc HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:MemberService.service.livelink.opentext.com/CreateMember"
Host: changedforposting
Content-Length: 832
Expect: 100-continue
Accept-Encoding: gzip, deflate

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:OTAuthentication xmlns:h="urn:api.ecm.opentext.com" xmlns="urn:api.ecm.opentext.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<AuthenticationToken><REMOVED></AuthenticationToken>
</h:OTAuthentication>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<CreateMember xmlns="urn:MemberService.service.livelink.opentext.com">
<member xsi:type="User">
<CreatedBy>0</CreatedBy><Deleted>false</Deleted><ID>0</ID>
<Name>newuser0</Name>
<DepartmentGroupID>1001</DepartmentGroupID>
<Password>mypassword</Password>
<TimeZone xsi:nil="true"/></member>
</CreateMember>
</s:Body>
</s:Envelope>

The reply was like this which I reckon is it is saying it is happy and complied,See where I highlight I am not sure if that is something that you need to set.I got my user created hope that helps somewhat.

HTTP/1.1 200 OK
Content-Length: 876
Content-Type: text/xml; charset=utf-8
Server: Microsoft-IIS/7.5
Persistent-Auth: true
X-Powered-By: ASP.NET
Date: Tue, 21 May 2013 20:36:18 GMT

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header><h:OTAuthentication xmlns:h="urn:api.ecm.opentext.com" xmlns="urn:api.ecm.opentext.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AuthenticationToken><REMOVED></AuthenticationToken></h:OTAuthentication>
</s:Header>
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<CreateMemberResponse xmlns="urn:MemberService.service.livelink.opentext.com">
<CreateMemberResult xsi:type="User">
<CreatedBy>0</CreatedBy>
<Deleted>false</Deleted>
<ID>54465</ID>
<Name>newuser0</Name>
<DepartmentGroupID>1001</DepartmentGroupID>
<Password>mypassword</Password><TimeZone xsi:nil="true"/>
</CreateMemberResult>
</CreateMemberResponse>
</s:Body>
</s:Envelope>

Kyle_Swidrovich

Hi Bohdan,

SOAPUI is notoriously bad for not understanding inheritance.

As Appu noted earlier, my MemberService example notes that the superclass “Member” is what the MemberService methods accept, however, you need to pass in a specific implementation of a Member, such as User or Group.

So you’ll need to find a way to pass in a “Group” object instance, as a subclass of Member.

Kyle

Bohdan_Hanchuk

HI Appu,

Thanks very much.

Adding the missing xsi:Type="User" attribute and value to the member element, did the trick.

I don't believe I would have been able to discover/unovover this without doing what you did ... intercepting and inspecting the generted SOAP package.

Thanks again for your time and efforts ... much appreciated.

Cheers

Bohdan

Bohdan_Hanchuk

Hi Kyle,

As mentioned in my last reply to Appu we were able to determine how "Group" object instance manifests itself within SOAP package i.e. by including type attribute in <member xsi:type="Group"> .

I agre with your comment on SoapUI. I also realized what a I might be missing and approach to determine it by looking at your C# code.

Slight but critical correcction to my last reply to Appu ... the attribute name is all lower case i.e. type not Type.

Thanks

Bohdan

eLink User

Glad it worked many OT people also replied

So they deserve good mention as well

I learned something with Fiddler on the roof

Great tool

Kyle and all the others helping

You are my heroes

Sent from my iPhone

On May 21, 2013, at 4:34 PM, "eLink Entry: Content Web Services Forum" <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : "User"> or Group are you missing that?
"User"> or Group are you missing that? Posted bybhanchuk@opentext.com (Hanchuk, Bohdan)On 05-21-2013 17:31

HI Appu, Thanks very much. Adding the missing xsi:Type="User" attribute and value to the member element, did the trick. I don't believe I would have been able to discover/unovover this without doing what you did ... intercepting and inspecting the generted SOAP package. Thanks again for your time and efforts ... much appreciated. Cheers Bohdan
[To post a comment, use the normal reply function]
Topic: CreateMember fails with fault message "Member type must be user or group"
Forum: Content Web Services Forum
Content Server: Knowledge Center

Abdul_Rahaman

Hi Bohdan,

Can you please share the code, It ill be great help. we are also doing similar kind of implementation.

Thanks in Advance,

Best Regards,
AR