5.2's RESTful WS Plugin

Classic Servoy
1

Two questions:

1). Is it backwards compatible with 5.1.4?
2). Can I specify the exact serialized-data response body or will the plugin still serialize things as it wants to?

Please advise and thanks.

2

1> yes
2> no changes have been made to the plugin other than the onces listed in the release notes

3

Thank you Johan.

4

Hello,

I just migrate from 5.1 to 5.2 and all responses that I receive when I make request to the RESTful plug-in are HTTP 404 Not Found.

I manage to authenticate through HTTP Basic authentication and it works fine, the server response with HTTP 401, in case of an unauthorized user, but for an authorized user also receive 404.

Anyway, please help me with the 404 response. I don’t receive anything else but this.

Greetings,
Bogdan.

5

Hi again,

If I set the loginSolutionName property to none, it works. How can we still make it works with the loginSolutionName set to a module that we use for login?

Regards,
Bogdan.

6

Any help on this issue? Is pretty urgent for us as we can’t use the WS anymore.

Thank you!
Gabriel - Iulian Dumbrava

7

The authentication supports validates the credentials send with the request against the users stored in Servoy’s built-in security. It doesn’t support solutions that require authentication.

Paul

8

Thank you Paul.
So I understand that my solution is to take out the WS forms from my custom authentication application, and create another application which would hold the WS forms.

Is that correct?

Thanks again!
Gabriel - Iulian Dumbrava

9

I’m not exactly following what you mean.

The solution used by the RESTful WS plugin should NOT require authentication.

Paul

10

Hi,

Until now, when update to Servoy 5.2, we keep the forms that we used for RESTful API in the same solution with the application, and works fine. We never had other solution only for the RESTful WS.
Now, with Servoy 5.2 we changed the login mechanism to use the Login and Authenticator solutions, we set the loginSolutionName with our login solution and mustAuthenticate to true, so the RESTful WS doesn’t work.

So as you say, actually we have to place the RESTful WS forms in other solution with mustAuthenticate to false.

Greetings,
Bogdan.

11

Yes, the forms providing the RESTfull WebService implementation need to be exposed to the plugin through a solution that doesn’t require authentication.

Paul