You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/12/01 13:14:01 UTC

[jira] [Commented] (KNOX-1120) Pac4J Stop Using ConfigSingleton

    [ https://issues.apache.org/jira/browse/KNOX-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274363#comment-16274363 ] 

ASF subversion and git services commented on KNOX-1120:
-------------------------------------------------------

Commit 55be159283d77b382fa3325df5987410548640c9 in knox's branch refs/heads/master from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=55be159 ]

KNOX-1120 - Pac4J Stop Using ConfigSingleton

> Pac4J Stop Using ConfigSingleton
> --------------------------------
>
>                 Key: KNOX-1120
>                 URL: https://issues.apache.org/jira/browse/KNOX-1120
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: KnoxSSO
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>            Priority: Blocker
>             Fix For: 0.14.0
>
>
> We need to stop using the ConfigSingleton in Pac4J now that we have upgraded to 2.1.0. The use of the singleton has implications on hosting multiple Pac4J configurations across topologies in the same Gateway instance.
> Since the config is now being set on the SecurityFilter we should be able to migrate away from the singleton.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)