You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "ASF subversion and git services (JIRA)" <ju...@ws.apache.org> on 2013/11/05 04:19:17 UTC

[jira] [Commented] (JUDDI-686) track and map requestors IP address to auth token

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

ASF subversion and git services commented on JUDDI-686:
-------------------------------------------------------

Commit 1538859 from [~spyhunter99] in branch 'juddi/trunk'
[ https://svn.apache.org/r1538859 ]

JUDDI-686 done
JUDDI-637 adding some class level docs
JUDDI-691 fixed
JUDDI-644 flipping serialization flag for tck tests to reduce logging

> track and map requestors IP address to auth token
> -------------------------------------------------
>
>                 Key: JUDDI-686
>                 URL: https://issues.apache.org/jira/browse/JUDDI-686
>             Project: jUDDI
>          Issue Type: Improvement
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>             Fix For: 3.3
>
>
> basically, we can make auth token's a bit more secure by obtaining the requestor's ip address and store that along with the auth token (server side). upon validating an new request, we can then compare IP addresses. if they are different, invalidate the token and force reauthentication 



--
This message was sent by Atlassian JIRA
(v6.1#6144)