You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Pawel Pesz (JIRA)" <ji...@apache.org> on 2008/01/11 12:07:34 UTC

[jira] Created: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

User object created in PipelineSecurityHandler is missing additional data
-------------------------------------------------------------------------

                 Key: COCOON-2159
                 URL: https://issues.apache.org/jira/browse/COCOON-2159
             Project: Cocoon
          Issue Type: Bug
          Components: Blocks: Authentication Framework
    Affects Versions: 2.1.11
            Reporter: Pawel Pesz
            Priority: Minor
         Attachments: PipelineSecurityHandler.java.diff

When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

Posted by "Pawel Pesz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pawel Pesz updated COCOON-2159:
-------------------------------

    Attachment: PipelineSecurityHandler.java.patch

> User object created in PipelineSecurityHandler is missing additional data
> -------------------------------------------------------------------------
>
>                 Key: COCOON-2159
>                 URL: https://issues.apache.org/jira/browse/COCOON-2159
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Authentication Framework
>    Affects Versions: 2.1.11
>            Reporter: Pawel Pesz
>            Priority: Minor
>         Attachments: PipelineSecurityHandler.java.patch
>
>
> When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

Posted by "Pawel Pesz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pawel Pesz updated COCOON-2159:
-------------------------------

    Attachment: PipelineSecurityHandler.java.diff

> User object created in PipelineSecurityHandler is missing additional data
> -------------------------------------------------------------------------
>
>                 Key: COCOON-2159
>                 URL: https://issues.apache.org/jira/browse/COCOON-2159
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Authentication Framework
>    Affects Versions: 2.1.11
>            Reporter: Pawel Pesz
>            Priority: Minor
>         Attachments: PipelineSecurityHandler.java.diff
>
>
> When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

Posted by "Pawel Pesz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pawel Pesz updated COCOON-2159:
-------------------------------

    Attachment:     (was: PipelineSecurityHandler.java.diff)

> User object created in PipelineSecurityHandler is missing additional data
> -------------------------------------------------------------------------
>
>                 Key: COCOON-2159
>                 URL: https://issues.apache.org/jira/browse/COCOON-2159
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Authentication Framework
>    Affects Versions: 2.1.11
>            Reporter: Pawel Pesz
>            Priority: Minor
>         Attachments: PipelineSecurityHandler.java.patch
>
>
> When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed COCOON-2159.
------------------------------------

    Resolution: Fixed

> User object created in PipelineSecurityHandler is missing additional data
> -------------------------------------------------------------------------
>
>                 Key: COCOON-2159
>                 URL: https://issues.apache.org/jira/browse/COCOON-2159
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Authentication Framework
>    Affects Versions: 2.1.11
>            Reporter: Pawel Pesz
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>         Attachments: PipelineSecurityHandler.java.patch
>
>
> When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COCOON-2159) User object created in PipelineSecurityHandler is missing additional data

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COCOON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated COCOON-2159:
-------------------------------------

    Assignee: Carsten Ziegeler

> User object created in PipelineSecurityHandler is missing additional data
> -------------------------------------------------------------------------
>
>                 Key: COCOON-2159
>                 URL: https://issues.apache.org/jira/browse/COCOON-2159
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Authentication Framework
>    Affects Versions: 2.1.11
>            Reporter: Pawel Pesz
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>         Attachments: PipelineSecurityHandler.java.patch
>
>
> When an authenticated User object is created it can contain additional attributes specified inside the <data/> element produced by an authentication resource. Current code (i.e. PipelineSecurityHandler.java) doesn't read them correctly because an absolute node reference is used instead of a relative one. Luckily fixing this bug couldn't have been more trivial :)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.