This is the curl message from postman: curl -X POST \ http://localhost:8080/userManagement/rest/Traffic/users2 \ -H 'Authorization: Basic dG9tY2F0OnMzY3JldA==' \ -H 'Cache-Control: no-cache' \ -H 'Content-Type: application/json' \ -H 'Postman-Token: 71819f33-6206-02c5-5cf2-8de6347fc154' \ -d '[{"id":1, "code":2, "time":"2009-02-15", "cycleSecond":22, "programNumber":1221, "stageNumber":22, "moves":"22", "detectors":"fead","conditions":"2ddsa"}]'
On Mon, Apr 30, 2018 at 11:42 AM, Ognjen Blagojevic < [email protected]> wrote: > Zahi, > > On 25.4.2018. 13:19, [email protected] wrote: > >> I configured in my conf\server.xml file the realm as below: >>> >> > Ok, so the configuration looks fine. > > You said you are using Postman to send the request. Can you paste the > `curl` command that the postman can generate for you just to check if it > looks Ok? > > For instance, this would be the right curl command: > > curl -u admin:falcon -X POST http://your.server/webapp/ > > While those are not: > > curl -u admin:falco -X POST http://your.server/webapp/ (typo in > password, HTTP 401) > > curl -X POST http://your.server/webapp/ (no credentials specified, HTTP > 401) > > curl -u tomcat:s3cret -X POST http://your.server/webapp/ (wrong role, > HTTP 403) > > curl -u admin:falcon -X GET http://your.server/webapp/ (GET instead of > POST, HTTP status code... it depends) > > -Ognjen > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
