Named Query returns a "Query does not exist" error with API key authentication only
Cédric BLANC
started a topic
about 2 years ago
I have a Named Query that i use via postman, it work well with basic authentification but when i use API KEY, i have an error : "Query MyQuery does not exist". When I analyse, I observe in my filter I check if the request parameter match a value which is in a reference to a basic entity and when i remove this part of the filter, it work I dont have the error. How can this difference in behavior be explained? thank you in advance.
Best Answer
C
Cédric BLANC
said
about 2 years ago
Make sure that you have selected the Roles to grant in your API key configuration:
1 Comment
Cédric BLANC
said
about 2 years ago
Answer
Make sure that you have selected the Roles to grant in your API key configuration:
Cédric BLANC
I have a Named Query that i use via postman, it work well with basic authentification but when i use API KEY, i have an error : "Query MyQuery does not exist". When I analyse, I observe in my filter I check if the request parameter match a value which is in a reference to a basic entity and when i remove this part of the filter, it work I dont have the error. How can this difference in behavior be explained? thank you in advance.
Make sure that you have selected the Roles to grant in your API key configuration:
Cédric BLANC
Make sure that you have selected the Roles to grant in your API key configuration:
-
Import Data Into Entities via Azure Data Lake
-
Recover Deleted(soft Delete) Record and Configure in Application
-
Data Quality in batch mode and real-time integration
-
Integration with analytics tools
-
Query/Load/Delete data with the REST API
-
Does the Done Tab in Inbox have a limit?
-
How Can I Trigger Enricher or Sql Procedure when deleting?
-
Matching Rules But Only The Latest Record Creates a Golden Record
-
Unstructured and Semi Structured Data in Semarchy?
-
Read CSV files from AWS S3
See all 72 topics