You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Misagh Moayyed (Jira)" <ji...@apache.org> on 2022/06/03 14:21:00 UTC

[jira] [Resolved] (SYNCOPE-1681) Support LDAP Google Auth Tokens/Accounts in WA

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

Misagh Moayyed resolved SYNCOPE-1681.
-------------------------------------
    Resolution: Fixed

> Support LDAP Google Auth Tokens/Accounts in WA
> ----------------------------------------------
>
>                 Key: SYNCOPE-1681
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1681
>             Project: Syncope
>          Issue Type: New Feature
>          Components: wa
>    Affects Versions: 3.0.0
>            Reporter: Misagh Moayyed
>            Assignee: Misagh Moayyed
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Registration records, tokens, etc that are relevant for google authenticator as an mfa provider should be optionally stored in an LDAP backend for Syncope WA. 
> The LDAP support for GAuth already exists:
> [https://apereo.github.io/cas/6.5.x/mfa/GoogleAuthenticator-Authentication-Registration-LDAP.html]
>  
> The task here is to augment the google auth configuration to support appropriate LDAP settings, and then conditionally activate the module when settings specified. If settings are undefined, we defer to Syncope as the backend service (which is the default today)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)