Most elements of the Mavryx system require authorization; all requests without a valid token are rejected.
In the Mavryx system, we use token authentication based on the RFC 6750 specification for this purpose.
Each request to secured resources requires sending an authorization token in the header, as shown in the example below.
GET /resource HTTP/1.1
Host: resource.mavryx.solutions
Authorization: access_token eyJhbGciOiJSUzI1NiIsInR5cCI6ImFwcGxpY2F0aW9uL29hdXRoMithY2Nlc3NfdG9rZW4rand0In0.eyJqdGkiOiIyYTIwNTBjNi1hYmU5LTRkM2YtOTVmYy03NWNkMWNjY2FiNWEiLCJpc3MiOiJodHRwczpcL1wvYXV0aC1kZXYubWF2cnl4LnNvbHV0aW9ucyIsImF1ZCI6WyIqLm1hdnJ5eC5zb2x1dGlvbnMiLCIqLm1hdnJ5eC5zb2Z0d2FyZSJdLCJuYmYiOjE3MTI1MzU3NzEsImlhdCI6MTcxMjUzNTc3MSwiZXhwIjoxNzEyNTM5MzcxLCJzdWIiOiJhdXRoLWRldi5tYXZyeXguc29sdXRpb25zXC9jbGllbnRcLzA2OWFhNDdiLTFkZDgtNDI3My04MGJhLTFiNGRhZGVhOGZmNCIsIm1yeF9jaWQiOiJlZTI1YjkwNC1lMGZlLTRkOTEtOTkxMy04NWQxNDk2YTg3NjUiLCJtcnhfdWlkIjoiZjg4NzQyMzAtNzM3YS00ZjA1LWJkN2MtYzZiOGUwMTRjYzEwIiwibXJ4X3R5cCI6InVzZXIiLCJtcnhfdm90cCI6dHJ1ZSwic2NvcGUiOlsiYWNjb3VudDptZToqIl19.VJXqA2M792N7864sZ6jIFI6j1eLwQms-K_LaKYBwXaKXGAqRLtPkKqQlNtOGD9T35tJJuTH5QUZv6053PPL8cL1IiM-QUVyhpRaPrPWRGLVyR-uJLKbhkgu1ypvhMbwudoRgItJKAk_CIso9643V5Pe_wsTIH-v5lptBkLj4ULEhUSKBB_rz5YcEjjlUUiFEWGgeM0SlBcAoERy4nJEB8R92xlk00lR8ch7l3XLYW5HQo38WQpofO5lwfSl84JKuFWiGexK1rzs7TlfMIHOqdMRhsVSBbR1wtWThaXiOLHgrDF49c17IC37AKuK4VrHw9DFzJe7ZNb_0lh4Ld8he2ANot sending the token in the header will result in an error.
HTTP/1.1 401 Unauthorized