135.1 REST API security
135.1 REST API security
Welcome
To
Network for you
REST API security
We, as network engineers usually use the command-line interface (CLI) or a GUI to configure or monitor our
network devices.
• Parsing show and debug commands with scripts is difficult because these commands are for humans.
• To interact with applications or network devices, we can use an Application Programming Interface
(API).
• An API is a software interface which allows other applications to communicate with our application.
POST: Submits data to the specified resource to process. The POST method can also create new resources.
HTTP is popular so you can use REST APIs in almost any programming language.
A resource is a “thing” you can access and receive or change its representation.
On the web, this could be a document or image. With a REST API, it could be a row in a database.
We access a resource with a Uniform Resource Locator (URL). That’s right, the URLs we also use for websites.
- Client – Server architecture (The Client sends a request , the server sends a response)
- Uniform Interface: Provides simplicity.
- State less: no client context is stored one the server between requests.
- Cacheability: Responses must define themselves as either cacheable or non cacheable
- Layered system: any intermediary devices such as load balancers must be transparent to the
client and server.
- Code on demand : It is optional that is Servers can temporarily extend or customize the
functionality of a client by transferring executable code.
- NETCONF and RESETCONF are API specially designed to work with network devices.
Follow REST API rules ----→ like Stateless so we will not have any session open – Be Stateless