You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2014/01/21 17:13:20 UTC

[jira] [Comment Edited] (JUDDI-791) Login/Logout in admin and juddi-gui

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

Kurt T Stam edited comment on JUDDI-791 at 1/21/14 4:11 PM:
------------------------------------------------------------

If this is no error then we don't need a stack. Just an info/warning message will do in that case.

Also - the validation in the startupServlet seems fine:

Jan 21, 2014 10:56:59 AM org.apache.juddi.webconsole.StartupServlet contextInitialized
INFO: Attempting to generate 256 bit AES key
Jan 21, 2014 10:57:01 AM org.apache.juddi.webconsole.StartupServlet contextInitialized
INFO: 256 bit key validation failed.
Jan 21, 2014 10:57:01 AM org.apache.juddi.webconsole.StartupServlet contextInitialized
INFO: Attempting to generate 128 bit AES key
Jan 21, 2014 10:57:01 AM org.apache.juddi.webconsole.StartupServlet contextInitialized
INFO: Generation of 128 bit AES key successful

but can add some sort of WARN about why 256 failed? and hint on how to about fixing it? Like pointing to our docs?


was (Author: kurtstam):
If this is no error then we don't need a stack. Just an info/warning message will do in that case.

> Login/Logout in admin and juddi-gui
> -----------------------------------
>
>                 Key: JUDDI-791
>                 URL: https://issues.apache.org/jira/browse/JUDDI-791
>             Project: jUDDI
>          Issue Type: Bug
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.2
>
>         Attachments: JUDDI-791-patch.txt
>
>
> Can we add the username that is logged in, to the admin and juddi-gui? And then hide the login forms; and display a logout button? At the moment it is very hard to figure out if you have a valid session; and if you do have one how to invalidate it.
> Also let's talk about replacing the jUDDIAuthenticator with something just a bit more restrictive so at least the password is checked.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)