exo-ecm-dms

Constant warning in console regarding bonita when navgating the JCR using DAV

Details

  • Labels:
  • Similar issues:
    ECM-3838 [TEST] Constant warning in console regarding bonita when navgating the JCR using DAV
    ECM-3839 [DEV] Constant warning in console regarding bonita when navgating the JCR using DAV
  • Description:
    Hide

    I have unzipped the ECM 2.3 (tomcat/HSQL)

    Started the server
    Connect to the JCR using DAV

    and I see the following message when I do navigate in the JCR using DAV

    Mar 18, 2009 7:48:55 AM org.ow2.novabpm.identity.auth.SecurityContext setSubject
    WARNING: Subject is already set to: Subject:
    Principal: administrators
    Principal: users
    Principal: organization
    Principal: root
    Public Credential: org.exoplatform.services.security.UsernameCredential@63dc35
    Private Credential: exo
    . Did you logout before login?

    Show
    I have unzipped the ECM 2.3 (tomcat/HSQL) Started the server Connect to the JCR using DAV and I see the following message when I do navigate in the JCR using DAV
    Mar 18, 2009 7:48:55 AM org.ow2.novabpm.identity.auth.SecurityContext setSubject WARNING: Subject is already set to: Subject: Principal: administrators Principal: users Principal: organization Principal: root Public Credential: org.exoplatform.services.security.UsernameCredential@63dc35 Private Credential: exo . Did you logout before login?
  • Environment:

    OSX

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Nicolas Filotto added a comment - 25/Jun/09 4:37 PM - edited

The clearSubject method has not been fixed properly, we still have

25 juin 2009 16:43:25 org.ow2.novabpm.identity.auth.SecurityContext clearSubject

ATTENTION: clearSubject() called but subject is already null!

Indeed in the code of BonitaStorageLoginModule we have:

if(subject != null) SecurityContext.clearSubject();

the local value of "subject" is never null

so we should have something like this:

if (SecurityContext.getSubject() != null) SecurityContext.clearSubject();

Show
Nicolas Filotto added a comment - 25/Jun/09 4:37 PM - edited The clearSubject method has not been fixed properly, we still have 25 juin 2009 16:43:25 org.ow2.novabpm.identity.auth.SecurityContext clearSubject ATTENTION: clearSubject() called but subject is already null! Indeed in the code of BonitaStorageLoginModule we have: if(subject != null) SecurityContext.clearSubject(); the local value of "subject" is never null so we should have something like this: if (SecurityContext.getSubject() != null) SecurityContext.clearSubject();

People

Dates

  • Created:
    18/Mar/09 7:04 AM
    Updated:
    23/Feb/10 7:46 AM
    Resolved:
    25/Jun/09 10:06 PM
    Date of First Response:
    25/Jun/09 4:37 PM
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for eXo Platform. Try JIRA - bug tracking software for your team.