In our collection, /clientId key is used as a partition key, setting the breakpoint at the first line of the insertion function gives this output, and aPartitionKey is printed as follows: I'm sure i'm passing the partitionKey correctly.
I've looked up on internet and found similar questions that seemed to be related to my problem like this and this, but they focus on passing the partitionKey correctly. I'm pretty sure i'm passing the partition key value correctly as i have the same createMany method which uses a stored procedure for bulk insertion and passes partitionKey in requestOptions, and it's working fine. Looking for an expert in HCL Domino, XPages, Angular, web, Notes client, mobile? Or need assistance in using any of my open source projects? Contact me.I get the above error: PartitionKey extracted from document doesn't match the one specified in the header. I live in the Netherlands and work for various national and internationalclients. I also work as a freelance webdeveloper/ consultant, specialising in Angular/ HCL (Lotus) Notes/ Domino/ XPages/ mobile/ Java/ app development. I set it to the hostname of the IBM Connections server and voila: happy times! After enabling that in Postman I was able to change the Origin header of my requests. This chrome extension is not supported or maintained by Postdot Technologies.
Accessed by clicking the postman icon in the Chrome toolbar. The header is one of the ‘restricted’ headers that is automatically added by the browser (Chrome) and can’t be easily changed. Luckily, the people at Postman also thought of that and created the “ Postman Interceptor“: a Chrome extension that sits as a sort of proxy between your Postman requests. No separate window required This is the legacy postman extension that can run in a Chrome tab.
POSTMAN CHROME PLUGIN HOW TO
So the only thing left (since I like testing with Postman), was to figure out how to change that Origin header. Using a curl command I could easily bypass the header and confirm that it was indeed the cause of my problem. That’s by design and has something to do with cross-site request forgery. Turns out that IBM Connections doesn’t really like that. Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop So by enabling the Chrome Developer tools for Postman, I was able to look at the exact HTTP request that Postman sends. And I found the Origin header that was already mentioned in the StackOverflow post: So, apparently there’s something fishy going on with Postman. My first thought was that it must be some strange access control setting hidden away deep in a config file (“don’t allow users to create stuff using the API”), but then I found someone with a similar issue on StackOverflow. The funny thing was that using the same credentials, I could create items using the web interface just fine. You are not authorized to perform the requested action. All GET and PUT requests came through fine, but I wasn’t able to create anything using a POST request to the API: every request I made returned a 403 error: While running the tests in Postman I ran into a big issue. My preferred application for that is Postman.
POSTMAN CHROME PLUGIN CODE
The Connections API is pretty complex, so I normally run some ‘manual’ tests first based on the documentation, and then use those result to write the code to call the API. More specifically: I wanted to show and create activities based on some user input. I was doing some work with an Angular application talking to the IBM Connections API.
0 kommentar(er)
