April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-64) Invalid redirect for resources from root context (domain management)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-64?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated WFLY-64: ----------------------------- Assignee: Darran Lofthouse (was: Thomas Diesler) > Invalid redirect for resources from root context (domain management) > -------------------------------------------------------------------- > > Key: WFLY-64 > URL: https://issues.jboss.org/browse/WFLY-64 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Currently accessing the admin console is resulting in a redirect similar to: - > {code} > HTTP/1.1 301 Moved Permanently > Connection: keep-alive > Content-Length: 0 > Location: http://localhost:9990/favicon.ico/console/index.html/console/index.html/c... > {code} > Instead this should result in a 404 Not Found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1150) Add file based auth to http management interface

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1150?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1150: ------------------------------- Assignee: Darran Lofthouse (was: Eduardo Martins) > Add file based auth to http management interface > ------------------------------------------------ > > Key: WFLY-1150 > URL: https://issues.jboss.org/browse/WFLY-1150 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Assignee: Darran Lofthouse > > usecase: allow clients using http api to use the file based auth so they do not have to rely on the binary protocol and remoting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-453) Add Version 2.0 of the jboss-as-config schema

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-453?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-453: ------------------------------ Assignee: Darran Lofthouse (was: Brian Stansberry) > Add Version 2.0 of the jboss-as-config schema > --------------------------------------------- > > Key: WFLY-453 > URL: https://issues.jboss.org/browse/WFLY-453 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Add version 2.0 of the domain management schema. > A few issues currently being worked on require this so we are splitting out the new version so they can all build on it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-438) Remove unused JBOSS_ENDORSED_DIRS variable from all scripts

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-438?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-438: ------------------------------ Assignee: Darran Lofthouse (was: Paul Ferraro) > Remove unused JBOSS_ENDORSED_DIRS variable from all scripts > ----------------------------------------------------------- > > Key: WFLY-438 > URL: https://issues.jboss.org/browse/WFLY-438 > Project: WildFly > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Various scripts contain a JBOSS_ENDORSED_DIRS variable which is never used: - > /bin]$ grep -r "ENDORSED" . > ./jdr.sh: JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` > ./add-user.sh: JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` > ./jconsole.sh: JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` > ./appclient.bat:set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed > ./add-user.bat:set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed > ./domain.bat:set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed > ./vault.sh: JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` > ./jdr.bat:set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed > ./standalone.bat:set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed > ./appclient.sh: JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"` -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-140) switching users between ejb calls does not work when the call originates from a remote client

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-140?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-140: ------------------------------ Assignee: Darran Lofthouse (was: Thomas Diesler) > switching users between ejb calls does not work when the call originates from a remote client > --------------------------------------------------------------------------------------------- > > Key: WFLY-140 > URL: https://issues.jboss.org/browse/WFLY-140 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Description of problem: > Switching users between ejb calls does not work when the call originates > from a remote client. In this case, both ejbs are on the same JBoss instance. > The use case looks like the following: > remote standalone client ---> unsecured ejb3 (switch user here) -> secured ejb3 > I tried to use both approaches outlined in Q10/A10 of the JBoss > Security FAQ [1] in order to establish a security context in > the unsecured ejb that should be used to invoke the secured ejb. > Neither approach worked in my testing. > When the same unsecured ejb is called from a web application (secured > or unsecured), then the user switching works correctly. > The ejb security code appears to work differently based on the client > type (standalone remote ejb client vs a web application). > I believe this is happening because the > org.jboss.as.security.service.SimpleSecurityManager.push method (called > by the SecurityContextInterceptor) is checking for an existing > RemotingContext and grabbing the security context from there even > though the security context that should be used appears to be getting > propagated correctly. > The following area of the code appears to be causing the issue. This > section of code is executed which causes the newly established security > context to be ignored: > if (RemotingContext.isSet()) { > // In this case the principal and credential will not have been set to set some random values. > SecurityContextUtil util = current.getUtil(); > Steps to Reproduce: > Create a test application that looks like the following: > remote client ---> unsecured ejb3 (switch user here) -> secured ejb3 > Actual results: > If the unsecured ejb is invoked from a remote client, the user switching that takes place in the first ejb is ignored. Replace the remote standalone client with a web application and the user switching works. > Expected results: > User switching should work if the client is a standalone remote client or a web application. > Additional info: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-319) OpenSSL SSL certificate support for domain management security realms (http and native interface)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-319?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-319: ------------------------------ Assignee: Darran Lofthouse (was: jaikiran pai) > OpenSSL SSL certificate support for domain management security realms (http and native interface) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-319 > URL: https://issues.jboss.org/browse/WFLY-319 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Security, Server > Reporter: Franck LEDAY > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > related to https://community.jboss.org/message/728665#728665 : > Request the feature to use SSL certificate issued from OpenSSL directly from SSL attribute of management interface instead of available use of JKS . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-474) Update the add-user.sh images to reflect the latest guided workflow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-474?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-474: ------------------------------ Assignee: Darran Lofthouse (was: Paul Gier) > Update the add-user.sh images to reflect the latest guided workflow > ------------------------------------------------------------------- > > Key: WFLY-474 > URL: https://issues.jboss.org/browse/WFLY-474 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > No point updating 7.1.x as EAP users don't get an image to guide them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-130) Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur."

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-130?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-130: ------------------------------ Assignee: Darran Lofthouse (was: Jason Greene) > Cygwin, add-user.sh and error "JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur." > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-130 > URL: https://issues.jboss.org/browse/WFLY-130 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Environment: Windows XP with CYGWIN_NT-5.1 ... 1.7.17 (0.262/5/3) 2012-10-19 i686 > Java HotSpot 1.7.0_11, RE build 1.7.0_11-b21, Client VM build 23.6-b04, mixed mode > JBoss AS 7.1.3.Final > Reporter: Bernard Giroud > Assignee: Darran Lofthouse > Labels: as7, management > Fix For: 8.0.0.Alpha1 > > > First of all, the add-user.sh script has an invalid syntax on line 14 which reads: > {code} > cygwin = true; > {code} > It should read: > {code} > cygwin=true; > {code} > without spaces around the equal sign, Otherwise the truth value is not set, and the conversion back to Windows pathes is not done. > Furthermore, the back-conversions should be conditioned to avoid a "cygpath: can't convert empty path" in lines 56-60, especially with JAVA_HOME. > Finally, issuance of the following command : bin/add-user.sh u p > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:107) > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:118) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:166) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Issuance of the following command : bin/add-user.sh > Gives: > {noformat} > cygpath: can't convert empty path > Exception in thread "main" java.lang.IllegalStateException: JBAS015232: Aucune java.io.Console disponible pour interagir avec l'utilisateur. > at org.jboss.as.domain.management.security.AddPropertiesUser.<init>(AddPropertiesUser.java:78) > at org.jboss.as.domain.management.security.AddPropertiesUser.main(AddPropertiesUser.java:168) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > {noformat} > Option --silent doesn't make a difference. > An obvious workaround exists though: use with a CMD windows > {noformat} > bin\add-user.bat u p > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-448) Authorization Checks for Services over Remoting

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-448?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-448: ------------------------------ Assignee: Darran Lofthouse (was: jaikiran pai) > Authorization Checks for Services over Remoting > ----------------------------------------------- > > Key: WFLY-448 > URL: https://issues.jboss.org/browse/WFLY-448 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Authorization > Fix For: 8.0.0.Alpha1 > > > As all services are now moving to be exposed over Remoting connectors they can all be secured using the same realm. This task is to ensure each at the very least has a basis for an authorization check that can be extended for more complex service specific requirements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-50) Management Console - LDAP authentication fails

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-50?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated WFLY-50: ----------------------------- Assignee: Darran Lofthouse (was: jaikiran pai) > Management Console - LDAP authentication fails > ---------------------------------------------- > > Key: WFLY-50 > URL: https://issues.jboss.org/browse/WFLY-50 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml > Reporter: narayana b > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > 1) security realms >  > <security-realm name="my_Ldap_Realm"> > <authentication> > <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com"> > <username-filter attribute="sAMAccountName"/> >  > </ldap> > </authentication> > </security-realm> >  > 2) outbound connections >  > <outbound-connections> > <ldap name="my_Ldap_Connection" > url="ldap://localhost:10389/" > search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" /> > </outbound-connections> >  > 3) Management console info config >  > <native-interface security-realm="my_Ldap_Realm"> > <socket-binding native="management-native"/> > </native-interface> > <http-interface security-realm="my_Ldap_Realm"> > <socket-binding http="management-http"/> >  > > </http-interface> >  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013