You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by "Eric J. Christeson (JIRA)" <ji...@apache.org> on 2011/01/18 19:19:43 UTC

[jira] Created: (ESME-324) Login message not generated

Login message not generated
---------------------------

                 Key: ESME-324
                 URL: https://issues.apache.org/jira/browse/ESME-324
             Project: ESME
          Issue Type: Bug
         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
            Reporter: Eric J. Christeson


Logging in via open-id generates a login message:

User ejc logged in
public just now caused by login 

Logging with username/password works, but doesn't generate login message.  No errors are generated.



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


[jira] Closed: (ESME-324) Login message not generated

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

Dick Hirsch closed ESME-324.
----------------------------

    Resolution: Fixed

Has the added advantage that logins via the API are also tracked

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: Release 1.1
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: 1.2
>
>         Attachments: esme.patch
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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


[jira] Updated: (ESME-324) Login message not generated

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

Dick Hirsch updated ESME-324:
-----------------------------

    Affects Version/s:     (was: 1.2)
                       Release 1.1

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: Release 1.1
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: 1.2
>
>         Attachments: esme.patch
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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


[jira] Commented: (ESME-324) Login message not generated

Posted by "Dick Hirsch (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ESME-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984603#action_12984603 ] 

Dick Hirsch commented on ESME-324:
----------------------------------

Currently installed on Stax.

Please test

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: Release 1.1
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: 1.2
>
>         Attachments: esme.patch
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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


[jira] Updated: (ESME-324) Login message not generated

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

Ethan Jewett updated ESME-324:
------------------------------

          Component/s: Server
        Fix Version/s: Backlog
    Affects Version/s: Release 1.1

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: Release 1.1
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: Backlog
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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


[jira] Updated: (ESME-324) Login message not generated

Posted by "Eric J. Christeson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ESME-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric J. Christeson updated ESME-324:
------------------------------------

    Attachment: esme.patch

I found that the message generating code was only in UserAuth.scala in the open-id authentication.  I moved it to User.scala in logUserIn since this is called from password auth, openId, Rest, and API2 so it should cover all the bases.

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: Release 1.1
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: Backlog
>
>         Attachments: esme.patch
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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


[jira] Updated: (ESME-324) Login message not generated

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

Dick Hirsch updated ESME-324:
-----------------------------

    Affects Version/s:     (was: Release 1.1)
                       1.2
        Fix Version/s:     (was: Backlog)
                       1.2

> Login message not generated
> ---------------------------
>
>                 Key: ESME-324
>                 URL: https://issues.apache.org/jira/browse/ESME-324
>             Project: ESME
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.2
>         Environment: Running from sbt jetty-run and packaged and deployed on tomcat
>            Reporter: Eric J. Christeson
>             Fix For: 1.2
>
>         Attachments: esme.patch
>
>
> Logging in via open-id generates a login message:
> User ejc logged in
> public just now caused by login 
> Logging with username/password works, but doesn't generate login message.  No errors are generated.

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