[
https://issues.apache.org/jira/browse/SYNCOPE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353166#comment-14353166
]
ASF subversion and git services commented on SYNCOPE-651:
---------------------------------------------------------
Commit 3621adf44e6c76a4faefb9782f77d90a1707ac1e in syncope's branch
refs/heads/master from [~wimmelg]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=3621adf ]
[SYNCOPE-651] SyncopeUser:checkToken() should fail if token is not set on user
> SyncopeUser:checkToken() should fail if token is not set on user
> ----------------------------------------------------------------
>
> Key: SYNCOPE-651
> URL: https://issues.apache.org/jira/browse/SYNCOPE-651
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.1.8, 1.2.2
> Reporter: Guido Wimmel
> Assignee: Guido Wimmel
> Priority: Minor
> Fix For: 1.1.9, 1.2.3, 2.0.0
>
>
> Currently, SyncopeUser:checkToken(String token) always returns true if
> user.token==null (i.e., the token attribute is not set). This is
> counterintuitive if the token parameter is not null (as the token passed as a
> parameter is obviously not valid).
> To make workflow implementations more robust, SyncopeUser:checkToken(String
> token) should return false if the token parameter is not null and user.token
> is null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
