Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
10 replies
Subscribers
7 subscribers
Views
3958 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Not able to see endpoint URL for Web API developed in Appian 16.2. Is it somethi
saravanana
over 7 years ago
Not able to see endpoint URL for Web API developed in Appian 16.2. Is it something defect or disabled in 16.2? I do see URL for enpoints if Web API created before 16.1.. Any suggestion?
OriginalPostID-216923
OriginalPostID-216923
Discussion posts and replies are publicly visible
0
chandolum
A Score Level 1
over 7 years ago
Yes it's known defect, which I've raised in 16.2 webinar also, if we are using post method it is not showing URL, but if you use GET method it is showing the URL, when ever we are using POST we need to form the URL Manually, to get URL just change the method type as GET and copy the URL after copying, change the method type as POST. When ever we using write to data store it will take the method as POST by default.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
saravanana
over 7 years ago
Thanks for confirming.. It looks like one more efect for http POST and is throwing http 401 error for basic auth..it is working only inside test, not from outside REST API client
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Matthew Kornfield
Appian Employee
over 7 years ago
@Saravanan, this is an issue with authentication. If you run it through a REST client that supports preemptive authentication, the POST calls will work. The API only supports global authentication when using GET. The below snippet is the setting in SOAP-UI. The highlighted field would have need to be set for testing POST requests to Appian.
Also the endpoint, although it does not show for methods other than GET, is simply your key appended to
/suite/webapi/
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jims419
Certified Lead Developer
over 7 years ago
@Matthew, the issue is that you can't see the key after you've created a POST API, like you can with a GET.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
saravanana
over 7 years ago
Its not working even in SOAP UI for http post Web API created in 16.2.. getting 500 error in SOAP UI with premptive basic auth.. 401 error in postman without pre-emptive auth
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Matthew Kornfield
Appian Employee
over 7 years ago
@Jim Understood, it does not display the link with methods other than GET selected.
@Saravanan I don't know why you would be getting a 500 error without seeing more, but I believe the 401 error is from the fact that the auth is not pre-emptive.
https://forum.appian.com/suite/help/16.2/Web_APIs.html#Invoking_a_Web_API
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
saravanana
over 7 years ago
here is the details in logs "20:40:33,805 INFO [stdout] (ajp-/0.0.0.0:8009-2) 2016-06-09 20:40:33,804 [ajp-/0.0.0.0:8009-2] ERROR com.appiancorp.security.cors.CorsFilter - CORS request rejected; invalid request from 65.244.148.222 to /webapi
20:40:33,805 INFO [stdout] (ajp-/0.0.0.0:8009-2) javax.servlet.ServletException: CORS origin denied fhbjgbiflinjbdggehcddcbncdddomop not on allowed list:[demosite-samplenodejs.rhcloud.com]
20:40:33,805 INFO [stdout] (ajp-/0.0.0.0:8009-2) at com.appiancorp.security.cors.CorsFilter.handleNormalRequest(CorsFilter.java:289)
"
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
saravanana
over 7 years ago
It looks like , the reason was not able to invoke POST web API from SOAP UI.. it is looking for CORS settings for POST, PUT and DELETE requests. Is this valid assumption to make?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Matthew Kornfield
Appian Employee
over 7 years ago
I am not exactly sure. What I do know is I have seen that CORS request rejected when sending POST, PUT or DELETE without preemptive authentication.
Here is the knowledge base article on the issue.
forum.appian.com/.../kb-1011.html
If that is not the issue, it may be you have to change the CORS settings in the admin console, as indicated by this post (which addresses a different issue but involves the same CORS request rejected error):
forum.appian.com/.../e-177197
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
saksheer
over 7 years ago
I faced the same issue and followed the steps mentioned above. Got the URL by switching to GET method. Also with basic authentication, the web api call works in SOAP UI, if selected preemptive authentication.
Thanks for the informative post!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel