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

Problem executing the HelloWorld client

Kevin_Royere

Hello everyone,

I've been studying the web services possibilities of Content Server 10 for two weeks now, with no particular builder knowledge.

So I followed the SDK tutorial in order to test the HelloWorld web service with the provided C# solution. Here's what I've done until now :

- Install HelloWorld web service as a module into CS10
- On the builder, launch the _GenerateSource function
- Compile these sources with the provided ANT script
- Deploy the resulting web service into the IIS 7 web server, via a new application (not a virtual directory because I can't access the HelloWorld.svc otherwise)

After that I wanted to test the HelloWorld web services by launching the HelloWorldClient C# project. I run it and click on the button, and after a while an empty windows pops up with the title "Error".

I can't manage to find what I did wrong, could someone please give me a hint ? The corresponding builder log is attached.

thread0.out

Find more posts tagged with

Comments

Kyle_Swidrovich

Hi Kevin,

The thread log you provided has the following buried in it:

So your authentication isn’t working.

Not the Authentication service part, but rather the use of the token AuthenticateUser(“Admin”, password) provided back to you for use with your HelloWorld.GetMessage() call.

You can see from the log line noted above that using that token, for some reason, we can’t figure out what user that token belongs to.

I don’t know what your encryption key is for cookies, nor do I know what cookie security settings you have, so I can’t see if the cookie data is well formed.

Are you able to do something simple with the shipping DocumentManagement service (like GetNode(2000)) with the same token?

Cheers,

Kyle

Kyle_Swidrovich

One other thing I’ll mention is that it took 25 seconds before that error message came back.

That could indicate that Content Server is timing out trying to do something server-side...

Kevin_Royere

Hi Kyle, and thanks for your clear and accurate answer.

Before trying to accomplish the HelloWorld Service tutorial, I successfully ran the LLTreeView C# sample project.

This sample uses services like Authentication, DocumentManagement and MemberService, and everything seems to work well (I just had to install a patch because I encountered a "The parameter is incorrect" error due to Directory Services module activated). However, the LLTreeView project doesn't point to the same IIS application than the HelloWorld project, so maybe it means nothing.

I'll try to call DocumentManagement service from the HelloWorld project to see if I got same results (to be updated)

I noticed that while LLTreeView is running, the REMOTE_ADDR variable is always the same (192.168.78.1) for each service call. However, in the HelloWorld log, the REMOTE_ADDR of the GetMessage service call has changed to an IP V6 like string.

Also, where can I see or change cookie configuration ? Does it concern IIS or the HelloWorld project ?

Again, thank you for your attention.

Regards,

Kevin

Kyle_Swidrovich

Hi Kevin,

The cookie configuration settings are within Content Server’s Security Administration page.

This can be accessed from the Admin Index page (?func=admin.index) of the Content Server installation.

If IP addresses are stored in the cookie, they will be used for validation of the cookie.

The token obtained through AuthenticateUser() will use the same rules.

This means that a token created under IPv4 (192.168.78.1) will fail to authenticate a request from an IPv6 address.

You can test this by disabling use of the IP in the authentication cookie in your test environment from the security page.

Content Server only supports use of one family of IP protocols – either IPv4 or IPv6, but not a mixed environment (now you can see whyJ).

Make sure your calls to AuthenticateUser() and GetMessage() follow the same network path to ensure a consistent IP protocol.

Cheers,

Kyle

Kevin_Royere

Hi Kyle,

Thanks, I now understand why I get this error. I disabled the use of IP in cookies, and now I receive the HelloWorld messages. There is just a SDO error that I don't understand, but this doesn't block anything (log is attached, FYI).

However, have you any hints about where that wierd IPV6 address comes from ?

When I launch the LLTreeView sample from the same workstation, the IP is always the good one and everything works well, so I guess something is wrong with the HelloWorld project ? I didn't change anything inside though.

How do I make sure that AuthenticateUser() and GetMessage() follow the same network path ?

Regards,

Kevin

thread0.out

Kyle_Swidrovich

Hi Kevin,

That IPv6 address is coming from your client machine – the one running your test application.

Not sure why LLTreeView is always using IPv4, unless your LLTreeView is connecting to a different web server.

To absolutely guarantee yourself that you’re not using an unsupported mixed environment, you first choose a protocol to go with (either IPv4 or IPv6) and then remove the extra protocol from the server OS – the server hosting Content Server.

This will ensure that Content Server will only accept connections via one protocol.

You can try to coerce Content Server into using one protocol over another if both are available on the machine by choosing a family hint on the “Specify Server Port” admin page (?func=admin.portcfg).

This is only a hint though. So if it can’t establish a listening socket on what you’ve selected, it will fall back on the other protocol option on the box.

Cheers,

Kyle

Kevin_Royere

Hello,

I disabled the TCP IPv6 protocol on the station which hosts Content Server. In addition, I set on the admin page the hint like you suggested, to coerce Content Server to use IPv4 in priority.

I restarted the host station and Content Server, and tried again to launch the Hello World project.

This time there is no more a wierd IPv6 address in the REMOTE_ADDR variable, but "::1". After a brief search, I found out that this is the equivalent of localhost for IPv6.

So it would mean that Content Server it-self fired the "GetMessage" request...

Any idea why I get this behaviour ? Or where in the code the REMOTE_ADDR is set maybe ?

Thank you