TweetShareSharePin0 SharesThis post is part of a series that starts with this post. Withy having looked at a bunch of things we can do with something as simple as an Auto-REST enabled view up to and including adding security, I just want to finish off with showing that having a view in the first place is not needed If all you want is a GET-service for a SQL. AUTO-Rest gives you many more things automatically, both like all forms of […]
TweetShareSharePin0 SharesThis post is part of a series that starts with this post. In the last post we made the service secure beyond all recognition (sebar 🙂 ) or maybe better expressed as so secure that nobody has access. In this post we’ll look at how to set up access to it to allow just those we have given credentials to to have access. To access a protected service one need to use a client-definition. id + secret, pretty much […]
TweetShareSharePin0 SharesThis post is part of a series that starts with this post. Having gone through much of what can be done with a basic REST-service earlier in this series, it is time to look at securing the service. When you can access a service with noting noire than just the URL, then so can anyone else that has access to sen toe ORDS-server the URL. Not only can they read, but if the view allows writing then they can […]
TweetShareSharePin0 SharesThis post is part of a series that starts with this post. It is time to turn to query parameters. It expands on the end point to allow slicing and dicing what we get back. Or in other words it allows projection. Or in layman terms, you can supply a where-clause expressed in jSON. You can also define sorting and much more. query parameters are basically key-value pairs with an equal sign as the separator. THis sounds much more […]