add Client authentication

[mj3cheun]

modify graphistry react to take an initialized graphistry client-api class and login using the auth token attached to that class when the graphistry iframe is initialized.

e.g.

    import { Client, Dataset, EdgeFile, NodeFile } from '@graphistry/client-api';
    const client = new Client(GRAPHISTRY_USERNAME, GRAPHISTRY_PASSWORD, '', 'http', 'localhost' );

    return (
        <Graphistry
            client={client}
            ...
        />
    );

[dess890]

Should client support organization(s) auth or only personal accounts?

[vaimdev]

After a sync with Des, I believe we still need to enhance the viz app in order to get this work.

This function need to be enhanced to accept jwt token as query parameter to propagate the authentication into viz app

export function authenticateMiddleware(numRetry = 1) {}

[exrhizo]

@mj3cheun -- isn't it the case that normal auth attacheds a cookie to the domain, so can't they just get redirected to pick that up?

Why manually propogate the jwt between iframes?

[exrhizo]

I guess I don't get why they have an authenticated client object, but not auth w/ the server

It looks like the cookies are HttpOnly so I guess there would need to be a falcor route to allow the viz to send [csrftoken, graphistry_jwt] so those can get attached?

Or rather the jwt shouldn't need to go through the viz, and rather to some server route that attaches it to the domain cookies?

[exrhizo]

it would be simpler to attach the cookie to the domain but maybe with some drawbacks

• the end user would stay authenticated beyond the tab session (a malicious user could do this with any solution we are talking about)

If the token must be sent to the viz, postmessage is the secure way -- look at the node server to find it's middleware maybe it already accepts the jwt in a header, which would be the way to do this single session jwt auth