[jboss-jira] [JBoss JIRA] (WFLY-6798) Distributed single sign-on manager created twice per host

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-6798:
-------------------------------
    Description: While fixing an unrelated bug, I discovered that the distributable SSOManager is actually created twice per host - one is created for use with the single sign-on authentication mechanism, and a separate instance is created to handle session identifier changes.  I'm not entirely certain of the consequence of this (as the managers will share the same underlying infinispan cache), but it is definitely wrong and unintentional.  (was: While fixing an unrelated bug, I discovered that the distributable SSOManager is actually created twice per host - one is created for use with the single sign-on authentication mechanism, and a separate instance is created to handle session identifier changes.  I'm not immediately sure of the consequence of this (as the managers will share the same underlying infinispan cache), but it is definitely wrong and unintentional.)


> Distributed single sign-on manager created twice per host
> ---------------------------------------------------------
>
>                 Key: WFLY-6798
>                 URL: https://issues.jboss.org/browse/WFLY-6798
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Critical
>             Fix For: 10.1.0.Final
>
>
> While fixing an unrelated bug, I discovered that the distributable SSOManager is actually created twice per host - one is created for use with the single sign-on authentication mechanism, and a separate instance is created to handle session identifier changes.  I'm not entirely certain of the consequence of this (as the managers will share the same underlying infinispan cache), but it is definitely wrong and unintentional.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)