uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6085) DUCC Web Server (WS) login session should be coordinated amongst DUCC head nodes
Date Tue, 06 Aug 2019 11:44:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900923#comment-16900923
] 

Lou DeGenaro commented on UIMA-6085:
------------------------------------

Employ new table in DB to hole userid + login token.

Validate that user is authenticated by comparing browser userid + login token with that found
in DB.

Record userid + token in DB and browser cookies upon successful login.

Expire token in browser and delete entry from DB when user logs out.

Token lifetime is 1 century or until the user logs out, which ever comes first.

 

> DUCC Web Server (WS) login session should be coordinated amongst DUCC head nodes
> --------------------------------------------------------------------------------
>
>                 Key: UIMA-6085
>                 URL: https://issues.apache.org/jira/browse/UIMA-6085
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Major
>             Fix For: future-DUCC
>
>
> If a user logs in to WS when master-1 is the head node, then the head node switches to
master-2 the user must re-login.  The user would prefer that the login persist across head
nodes in the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message