Timeline for How can I successfully query the Content Service using its v4 odata endpoint?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2019 at 4:10 | comment | added | Sikarwar | @JaimeSantosAlcón Curious, what was the fix for "Error": "Invalid v4 service endpoint for content-service" ? | |
| Aug 14, 2018 at 16:36 | comment | added | Jaime Santos Alcón | I have a class that takes care of the OAuth part... and CIL doesn't seem to be working, so I might have something not properly configured... dunno what, though | |
| Aug 14, 2018 at 14:46 | comment | added | Atila Sos | @Harald, v2 is supported and can be used without any issues, for v4 I'm not certain. There are some valid use cases for directly using these endpoints. The biggest disadvantage of this approach however I would say is that you have to handle the OAuth part (initial authorization, token renewal when expired, etc.) manually (if the Content Service is protected that is). | |
| Aug 14, 2018 at 13:35 | comment | added | Jaime Santos Alcón | I am trying to avoid using the CIL libraries | |
| Aug 14, 2018 at 13:29 | history | answered | Harald Hoffelinck | CC BY-SA 4.0 |