428
97%

Ran 25 Nov 2016 01:39PM UTC

Jobs 2

Files 45

Run time 4s

Badge

Embed ▾

pending completion

Build # 428

Build Type

Pull #169

travis-ci

Committed by

web-flow

Commit Message

Fixes the check whether a user is actually locked.

Before, the user was claimed to be locked when any CASino::User sharing
the same username was locked. But a user is actually only locked, if he
does not have any CASino::User left, which is unlocked. The reason
herefore is, that he could have any secondary/legacy authentication
providers, on which he can never login. Therefore, one of his 'alter
egos' may be getting locked on any regular (and otherwise successful)
login attempt and he would be locked out regardless. That is now
changed, so that all CASino::Users sharing the same username must be
first be in locked state before one is considered locked.

Pull Request Pull Request #169: Lock user after a configurable amount of failed login attempts

Run Details

23 of 23 new or added lines in 4 files covered. (100.0%)

784 of 805 relevant lines covered (97.39%)

63.74 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	428.1 (2.1.0)	25 Nov 2016 01:39PM UTC	0	97.39	Travis Job 428.1
2	428.2 (2.2.2)	25 Nov 2016 01:39PM UTC	0	97.39	Travis Job 428.2

Source Files on build 428

Detailed source file information is not available for this build.

rbCAS / CASino / 428
97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 428

rbCAS / CASino / 428 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 428

rbCAS / CASino / 428
97%

README BADGES
x