directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FC-127) AuthN Validator
Date Fri, 11 Dec 2015 22:43:46 GMT

     [ https://issues.apache.org/jira/browse/FC-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shawn McKinney resolved FC-127.
-------------------------------
    Resolution: Fixed

> AuthN Validator
> ---------------
>
>                 Key: FC-127
>                 URL: https://issues.apache.org/jira/browse/FC-127
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC40
>            Reporter: Shawn McKinney
>             Fix For: 1.0.0-RC41
>
>
> Here's how it works.
> 1. create a new class, that extends org.apache.directory.fortress.core.util.AuthNValidator
> 2. implement the abstract method validate:
>     public int validate(Session session, Constraint constraint, Time time, VUtil.ConstraintType
type )
>     {
>         super.setRoleName( "AuthNUsers" );
>         return super.validate( session, constraint, time, type );
>     }
> Place the name of the role to verify.
> 3. add a new property to invoke your new class:
>                 <config props="temporal.validator.5:org.mine.util.AuthNUserValidator"/>
> 4. add the new class to runtime classpath of fortress
> 5. add the new role.
> 6. assign to users as needed.
> This validator will deactive the specified role iff the user is not authenticated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message