April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1065) Update GssapiClient to use CallbackHandler to obtain credential.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1065: ------------------------------------- Summary: Update GssapiClient to use CallbackHandler to obtain credential. Key: ELY-1065 URL: https://issues.jboss.org/browse/ELY-1065 Project: WildFly Elytron Issue Type: Enhancement Components: SASL Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.1.0.Beta36 The mechanism should attempt to obtain a credential from the CBH if one not supplied in the properties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat as Service

by Arunraj SRM (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1516?page=com.atlassian.jira.plugi... ] Arunraj SRM updated DROOLS-1516: -------------------------------- Summary: GAV names are not coming properly when running the tomcat as Service (was: GAV names are not coming properly when running the tomcat as Service with SSL) > GAV names are not coming properly when running the tomcat as Service > -------------------------------------------------------------------- > > Key: DROOLS-1516 > URL: https://issues.jboss.org/browse/DROOLS-1516 > Project: Drools > Issue Type: Bug > Components: build, kie server, tools > Affects Versions: 6.5.0.Final > Environment: Windows > Reporter: Arunraj SRM > Assignee: Toni Rikkola > Priority: Critical > Labels: Drools, GAV,, Maven > Attachments: gav_issue.png > > > Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as > <undetermined>:<undetermined>:<undetermined> > instead of actual path including the guvnor > Start-up values: > -Dcatalina.home=C:\apache-tomcat-9.0.0.M19 > -Dcatalina.base=C:\apache-tomcat-9.0.0.M19 > -Djava.io.tmpdir=C:\apache-tomcat-9.0.0.M19\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\apache-tomcat-9.0.0.M19\conf\logging.properties > -Xmx256M > -XX:MaxPermSize=2048m > -Dbtm.root=C:\apache-tomcat-9.0.0.M19\ > -Dbitronix.tm.configuration=C:\apache-tomcat-9.0.0.M19\conf\btm-config.properties > -Dbitronix.tm.resource.configuration=C:\apache-tomcat-9.0.0.M19\conf\resources.properties > -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry > -Djava.security.auth.login.config=C:\apache-tomcat-9.0.0.M19\webapps\kie-wb\WEB-INF\classes\login.config > -Dorg.jboss.logging.provider=jdk > -Dorg.jbpm.cdi.bm=java:comp/env/BeanManager > -Dorg.kie.server.persistence.ds=java:comp/env/jdbc/jbpm > -Dorg.kie.server.persistence.tm=org.hibernate.service.jta.platform.internal.BitronixJtaPlatform > -Dorg.uberfire.nio.git.dir=C:\drools\repositories\git\ > -Dorg.guvnor.m2repo.dir=C:\drools\repositories\kie\ > -Dorg.uberfire.metadata.index.dir=C:\drools\runtime\ > -Dorg.uberfire.nio.git.ssh.cert.dir=C:\drools\runtime\ > -Dorg.kie.demo=false > -Dorg.kie.example=false > -Dorg.kie.server.id=default-kieserver > -Dorg.kie.server.location=https://localhost/kie-server/services/rest/server > -Dorg.kie.server.controller=https://localhost/kie-wb/rest/controller > -Dorg.jbpm.server.ext.disabled=true > -Dorg.drools.server.filter.classes=true -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2349) Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients.

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2349?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2349: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Darran Lofthouse) > Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients. > --------------------------------------------------------------------------------- > > Key: WFCORE-2349 > URL: https://issues.jboss.org/browse/WFCORE-2349 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: ehsavoie Hugonnet > Fix For: 4.0.0.Alpha1 > > > Other services such as EJB and transactions have a Remote*Permission to verify the remote client has the required permission to use that service - this should be repeated for the management related services to control what a remote client can and can not connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8538) Remove need to configure default-virtual-host at subsystem level

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8538?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8538: ---------------------------------------- Don't doing anything on this without considering all the compatibility stuff, and then prioritize accordingly. > Remove need to configure default-virtual-host at subsystem level > ---------------------------------------------------------------- > > Key: WFLY-8538 > URL: https://issues.jboss.org/browse/WFLY-8538 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 11.0.0.Alpha1 > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > > There is currently needed host to which the deployments should be deployed by default. This is found out from default-virtual-host at undertow subsystem level. This value actually duplicates setting from the value set in default-host attribute of default server, as such it should be removed and thus config simplified by counting the needed value default server's default-host value. > CC [~ctomc] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2641?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2641: ---------------------------------------- Assignee: (was: Brian Stansberry) > Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-2641 > URL: https://issues.jboss.org/browse/WFCORE-2641 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 3.0.0.Beta13 > Reporter: Ondrej Lukas > Priority: Blocker > > When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and referenced security-realm does not include authentication, then authentication through http-interface is not possible. > When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed. > When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned: > {code} > { > "outcome" : "failed", > "failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error", > "rolled-back" : "true" > } > {code} > When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Component/s: SASL > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta36 > > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Fix Version/s: 1.1.0.Beta36 > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta36 > > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Description: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- was: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- -if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } - > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Description: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- {code:java} if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } {code}- was: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. -We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods: {code:java} if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } {code}- > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- > {code:java} > if (completed) { > throw new IllegalStateException( > "EXTERNAL supports neither integrity nor privacy"); > } else { > throw new IllegalStateException( > "Authentication not completed"); > } > {code}- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-802) Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-802?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-802: --------------------------------- Description: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- {code:java} -if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } -{code}- was: Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- {code:java} if (completed) { throw new IllegalStateException( "EXTERNAL supports neither integrity nor privacy"); } else { throw new IllegalStateException( "Authentication not completed"); } {code}- > Elytron ExternalSaslServer/Client should throw IllegalStateException for wrap/unwrap methods > -------------------------------------------------------------------------------------------- > > Key: ELY-802 > URL: https://issues.jboss.org/browse/ELY-802 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Darran Lofthouse > > Calling {{wrap/unwrap}} methods on {{ExternalSaslServer/Client}} should throw {{IllegalStateException}} as defines [the contract|http://docs.oracle.com/javase/8/docs/api/javax/security/sasl/Sas...]. Currently it throws a {{SaslException}}. > --We could be inspired by OpenJDK implementation of CRAM-MD5 and do the following in both methods:- > {code:java} > -if (completed) { > throw new IllegalStateException( > "EXTERNAL supports neither integrity nor privacy"); > } else { > throw new IllegalStateException( > "Authentication not completed"); > } > -{code}- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017