[
https://issues.apache.org/jira/browse/JUDDI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877563#comment-13877563
]
Kurt T Stam commented on JUDDI-791:
-----------------------------------
It seems to work but I get this stack in the logs:
2014-01-21 10:58:06,347 INFO [org.apache.juddi.gui] - Key validation failed!
java.security.InvalidKeyException: Illegal key size or default parameters
at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1011)
at javax.crypto.Cipher.implInit(Cipher.java:786)
at javax.crypto.Cipher.chooseProvider(Cipher.java:849)
at javax.crypto.Cipher.init(Cipher.java:1213)
at javax.crypto.Cipher.init(Cipher.java:1153)
at org.apache.juddi.adminconsole.AES.EN(AES.java:77)
at org.apache.juddi.adminconsole.AES.ValidateKey(AES.java:101)
at
org.apache.juddi.adminconsole.StartupServlet.contextInitialized(StartupServlet.java:42)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
2014-01-21 10:58:06,355 INFO [org.apache.juddi.Registry] - Starting jUDDI
registry...
> 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)
