Unless I’m mistaken, it seems that when using the RAML console (or in the preview in the API Designer) custom authentication is not an option under “Try it.”
A few thoughts here. First, I was hoping that it would be available after defining this in my RAML file:
describedBy: headers: Authorization: description: Used to send a valid token. Do not use with query string parameter type: string queryParameters: accesskey: description: Used to send a valid access token. Do not use together with header. type: string
(I also have
securedBy: at the root)
I was hoping that under “Try it” I would simple be able to enter in my access token here and the console would send it with the request. Unfortunately, it doesn’t even show up as an option.
I understand if the console doesn’t support custom authentication at all. If not, then what is the reason for including the security info in the RAML file? I would also prefer the “Try it” section being left blank or the tab not even showing up if I specify that the whole API is
securedBy (this would answer my first question). Currently it is showing “Authentication Type: Anonymous” which is confusing if anonymous authentication is what I am trying to avoid by marking
securedBy at the root.