JayStack OData V4 Server – basic authentication
- On 23rd February 2017
- Posted by admin
- JayData
Last time, we created a little example server to demonstrate computed properties. Now, we will extend that example with basic authentication using the popular Passport module and using the example server as an express.js router middleware.
Include Passport
First, we need to import some extra modules:
|
1 2 3 4 5 |
import { Edm, odata, ODataController, ODataServer, ODataErrorHandler, ODataHttpContext, HttpRequestError } from "odata-v4-server"; import * as express from "express"; import * as passport from "passport"; import { BasicStrategy } from "passport-http"; import { STATUS_CODES } from "http"; |
As you can notice, we imported new features from the odata-v4-server module, the ODataHttpContext interface and the HttpRequestError custom error class.
Configuration of the Passport layer is very simple, we implement our basic authentication verify function as this (the username and password will be hardcoded here):
|
1 2 3 4 |
passport.use(new BasicStrategy((userid:string, password:string, done:(error:any, user?:any) => void) => { if (userid == "admin" && password == "admin") return done(null, "admin"); done(new AuthenticationError()); })); |
If the authentication is successful, we call the done function with null as the error and admin as the user parameter. You can pass any type of user instance here, for simplicity, we use the username. We can use this later in the controller.
If the authentication fails, we pass a new AuthenticationError instance as the first parameter of done. This custom error class is very easy to implement using HttpRequestError from the odata-v4-server module.
|
1 2 3 4 5 |
class AuthenticationError extends HttpRequestError{ constructor(){ super(401, STATUS_CODES[401]); } } |
You just have to extend the HttpRequestError class and call the super constructor with an error status code and a message. The message will be the default message for status code 401, provided by the http built-in node.js module.
Accessing authenticated user
In the example People OData controller, you can access the authenticated user on the request object by using the context parameter decorator from the odata decorator system. The parameter type will be a ODataHttpContext so we can use the interface to get the type annotations of the context object.
|
1 2 3 4 5 6 7 8 9 10 11 |
@odata.type(Person) class PeopleController extends ODataController{ @odata.GET get(@odata.key id:number, @odata.context context:ODataHttpContext){ return { Id: id, FirstName: context.request.user, LastName: context.request.user }; } } |
Using the server as a middleware
As the last step, we wire up the express.js middlewares.
|
1 2 3 4 5 6 7 |
const app = express(); app.use( passport.authenticate("basic", { session: false, failWithError: true }), PeopleServer.create(), ODataErrorHandler ); app.listen(3000); |
In the previous example, we used the PeopleServer.create function to start a standalone HTTP server. This time, without using any parameters, we can access an express.js router middleware. To maintain OData standard error messages in our service, we need to add the ODataErrorHandler middleware as the express.js error handler. This way even if the authentication fails the response will be a standard OData error response. Finally we just start the express.js server on port 3000.
We created a very basic authentication example here, but you can extend this to implement more robust and advanced authentication for your OData server.
You can see the full working example here.
Source: JayData.org
0 Comments