2.0.4 • Published 2 years ago

@nicholasfulton/auth_accessor v2.0.4

Weekly downloads
-
License
ISC
Repository
bitbucket
Last release
2 years ago

Auth Accessor

Building

To build, run npm install followed by npm run build in the project directory. These commands will build the output module, in the auth directory. At this point the auth directory is ready to be moved to its destination.

Usage

Keys

In the root of the repository, keys.txt contains development keys for authenticating servers. In production, unique credentials will be generated with various scopes.

Setup

Place the auth folder in the project directory. Include a reference to accessor.js, a direct child of the auth directory. This contains a class definition which implements the interface defined in iaccessor.js. Its constructor accepts the server ID and server secret as parameters.

Example:

const auth = new (require('./auth/accessor').Accessor)(serverId, serverSecret);

// or 

const Accessor = require('./auth/accessor').Accessor;
const auth = new Accessor(serverId, serverSecret);

// use auth...

Check Session

This will check whether a user's session is valid without extending its duration or updating the user cookie (refreshing). The required parameters are the session ID and token which are encoded in the MDXS (Munidex session) cookie in the form {sessionId}:{sessionToken}.

Example:

// ...initialize auth

auth.isSessionValid(id, token).then(isValid => {
    if (isValid) {
        console.log("Session is valid!");
    }
    else {
        console.log("User needs to be redirected to signin");
    }
});

// or

let isValid = await auth.isSessionValid(id, token);
console.log(isValid ? "Session is valid!" : "User needs to be redirected to signin");

Refresh Session

Similar to check session, but the expiration timestamp on the session is to be extended both on database and in the user cookie. Not yet implemented.

Get User Info

This will, if a user's session is valid retreive a user's profile from the auth server using their session ID. In the future an option to retreive their profile offline, using their unique ID, will be added.

IMPORTANT: the current implementation retrieves the user info by their session ID rather than user ID

Example:

// ...initialize auth

auth.getUserInfo(id).then(profile => {
    console.log(profile);
}).catch(err => {
    console.log(err); // Most likely user is not signed in
});

// or

let profile = await auth.getUserInfo(id);
2.0.4

2 years ago

2.0.3

3 years ago

2.0.2

3 years ago

2.0.1

3 years ago

2.0.0

3 years ago

1.1.4

4 years ago

1.1.3

4 years ago

1.1.2

4 years ago

1.1.1

4 years ago

1.1.0

4 years ago

1.0.3

4 years ago

1.0.2

4 years ago

1.0.1

4 years ago

1.0.0

4 years ago