miniOrange API security with JWT (JSON web token) uses a JSON Object. In JWT Authentication, the JWT is provided by an OIDC provider after successful login, which is stored locally by the API gateway. This locally stored JWT is used to access the protected route or resource.
A JSON web token (JWT) used to securely transfer information over the web (between two parties). JWT (JSON Web Token) is mainly used for an authentication system, but it can also be used for information exchange.
JWT (JSON Web Token) is compact and self-contained for transferring information between systems using JSON objects.
Structure of JSON Web Token (JWT): JSON Web Tokens consist of three parts separated by dots (.) which are:
In JWT authentication, when the user successfully logs in using their credentials, a JWT (JSON Web Token) will be returned and must be saved locally (typically in local or session storage, but cookies can also be used), instead of the traditional approach of creating a session in the server and returning a cookie.
Whenever the user wants to access a protected route or resource, the user agent should send the JWT, typically in the Authorization header using the Bearer schema. The content of the header might look like the following:
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
This is a stateless authentication mechanism as the user state is never saved in server memory. The server’s protected routes will check for a valid JWT in the Authorization header, and if it is present, the user will be allowed to access protected resources.
As JWTs are self-contained, all the necessary information is there, reducing the need to query the database multiple times.
e.g. Authorization: Basic eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODk.SflKxwRJSMeKKF2QT4fwpM
We provide an option to enforce the use of HTTP over SSL in API requests, which transfer your credentials securely.
Validate request parameters on the very first step, before it reaches your API Server. Our strong validation checks blocks the access immediately if input validation fails, which helps to prevent SQL injection and other attacks.
We support the input validation specified by OWASP REST Security guidelines.
Along with other request parameters, we provide option to add a request timestamp as HTTP custom header in API request. The server will compare the current timestamp to the request timestamp, and only accepts the request if it is within the allowed timeframe (60-300 seconds). This will prevent replay attacks from attackers who are trying to brute force your system without changing this timestamp.
We support API requests and responses in signed manner as a added security.
API call with digitally signed requests make sure that API requests are coming from the trusted partner or client.
We protect your APIs with rate-limiting to mitigate distributed denial-of-service (DDoS)>/b> attacks and protecting the backend applications that process the API calls.