2
97%
master: 97%

Ran 25 Nov 2016 01:39PM UTC

Files 45

Run time 2s

Badge

Embed ▾

Committed 25 Nov 2016 01:36PM UTC coverage: 97.391% (+0.2%) from 97.201%

Job # 2.2.2

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

784 of 805 relevant lines covered (97.39%)

31.87 hits per line

rbCAS / CASino / 428 / 2
97%
master: 97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 428.2 (2.2.2)

rbCAS / CASino / 428 / 2 97% master: 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 428.2 (2.2.2)

rbCAS / CASino / 428 / 2
97%
master: 97%

README BADGES
x