September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-357) No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template

by Jan Blizňák (Jira)

[ https://issues.redhat.com/browse/WFWIP-357?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFWIP-357: ----------------------------------- This can be probably fixed just by adding additional trigger to either of BuildConfigs, eg. equivalent of this: {code:java} oc set triggers bc autoupgrading-app --from-image=eap7-runtime-imagestream:latest {code} But design decision needs to be made: # leave as is (probably not? - contrary to analysis) ## no rebuild when _only_ runtime image gets updated - we can argue how big issue it is as theoretically what needs to go to runtime image most likely is needed for builder image too, so it gets updated # add trigger to the second-in-chan BuildConfig ## quicker as only one build is triggered and intermediate resources reused ## requires intermediate imagestream to exist ## doesn't suffer from duplicated rebuild # add trigger to the first-in-chain BuildConfig ## safer as everything is build from scratch ## slower as two builds need to be done ## could suffer from double rebuild - when both builder and runtime image is updated > No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template > ------------------------------------------------------------- > > Key: WFWIP-357 > URL: https://issues.redhat.com/browse/WFWIP-357 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jeff Mesnil > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-357) No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template

by Jan Blizňák (Jira)

Jan Blizňák created WFWIP-357: --------------------------------- Summary: No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template Key: WFWIP-357 URL: https://issues.redhat.com/browse/WFWIP-357 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Jan Blizňák Assignee: Jeff Mesnil -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11717) Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-11717?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-11717. ------------------------------------- Fix Version/s: 21.0.0.Beta1 Resolution: Done I believe the JBoss Invocation upgrade in WildFly Core 13.0.0.Beta4 should have resolved this. WFCORE-4514 is still open to track so possible better code in this area, but the JBINV-9 fix should eliminate the warn. > Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory > --------------------------------------------------------------------------- > > Key: WFLY-11717 > URL: https://issues.redhat.com/browse/WFLY-11717 > Project: WildFly > Issue Type: Bug > Affects Versions: 15.0.1.Final > Reporter: Kris-Gerhard Aabrams > Assignee: Brian Stansberry > Priority: Major > Labels: Java11 > Fix For: 21.0.0.Beta1 > > > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/opt/jboss/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.1.Final.jar!/) to method java.lang.Object.clone() > WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1153) Can't configure empty base-dn for ldap realm

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFCORE-1153?page=com.atlassian.jira.plug... ] Sonia Zaldana reassigned WFCORE-1153: ------------------------------------- Assignee: Sonia Zaldana > Can't configure empty base-dn for ldap realm > -------------------------------------------- > > Key: WFCORE-1153 > URL: https://issues.redhat.com/browse/WFCORE-1153 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 2.0.2.Final > Reporter: Alberto Persello > Assignee: Sonia Zaldana > Priority: Major > Labels: authentication, authorization, group, ldap, realm > > It is not possible to set the empty value for base-dn attribute in authentication-->ldap element and in authorization-->ldap-->group-search-->group-to-principal element. > The empty value is the only valid option for java ldap searches to scan the entire ldap (the equivalent of RootDSE). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4540) Add error message with information that is not allowed to read secret-value and entry-type from Credential Store

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4540?page=com.atlassian.jira.plug... ] Farah Juma resolved WFCORE-4540. -------------------------------- Resolution: Rejected Resolving this one as "Rejected" since the corresponding JBEAP issue was rejected. > Add error message with information that is not allowed to read secret-value and entry-type from Credential Store > ---------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4540 > URL: https://issues.redhat.com/browse/WFCORE-4540 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Priority: Major > > Add error message with information that is not allowed to read secret-value and entry-type from Credential Store over CLI. > This CLI commands > {code} > /subsystem=elytron/credential-store=testCS/alias=someAlias:read-attribute(name=secret-value) > /subsystem=elytron/credential-store=testCS/alias=someAlias:read-attribute(name=entry-type) > {code} > end with success result. > {code} > { > "outcome" => "success", > "result" => undefined > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-6823?page=com.atlassian.jira.plugin... ] Farah Juma resolved WFLY-6823. ------------------------------ Resolution: Rejected Resolving this one as "Rejected" based on the last comment from Honza on this one. > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > ----------------------------------------------------------------------------------------- > > Key: WFLY-6823 > URL: https://issues.redhat.com/browse/WFLY-6823 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Priority: Major > > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603. > We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any information about it in specification. > It works with Chrome and Opera, but it doesn't work with Firefox. > Since there is no documentation for this username/password limitation it can affect customers who want to use non-ASCII credentials. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ] Sonia Zaldana edited comment on WFLY-11492 at 9/17/20 2:23 PM: --------------------------------------------------------------- The issue is that the Out of the Box component application-http-authentication was removed in WildFly 14. The solution is to configure an http-authentication-factory similar to the previous out of the box component. was (Author: szaldana): The issue is that the Out of the Box component ``application-http-authentication`` was removed in WildFly 14. The solution is to configure an ``http-authentication-factory`` similar to the previous out of the box component. > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.redhat.com/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation, Security > Reporter: Alan Hantke > Assignee: Sonia Zaldana > Priority: Major > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ] Sonia Zaldana edited comment on WFLY-11492 at 9/17/20 2:23 PM: --------------------------------------------------------------- The issue is that the Out of the Box component *application-http-authentication* was removed in WildFly 14. The solution is to configure an *http-authentication-factory* similar to the previous out of the box component. was (Author: szaldana): The issue is that the Out of the Box component application-http-authentication was removed in WildFly 14. The solution is to configure an http-authentication-factory similar to the previous out of the box component. > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.redhat.com/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation, Security > Reporter: Alan Hantke > Assignee: Sonia Zaldana > Priority: Major > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ] Sonia Zaldana commented on WFLY-11492: -------------------------------------- The issue is that the Out of the Box component ``application-http-authentication`` was removed in WildFly 14. The solution is to configure an ``http-authentication-factory`` similar to the previous out of the box component. > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.redhat.com/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation, Security > Reporter: Alan Hantke > Assignee: Sonia Zaldana > Priority: Major > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11492) Quickstart http-custom-mechanism: documentation step fails

by Sonia Zaldana (Jira)

[ https://issues.redhat.com/browse/WFLY-11492?page=com.atlassian.jira.plugi... ] Sonia Zaldana updated WFLY-11492: --------------------------------- Git Pull Request: https://github.com/wildfly/quickstart/pull/444 > Quickstart http-custom-mechanism: documentation step fails > ---------------------------------------------------------- > > Key: WFLY-11492 > URL: https://issues.redhat.com/browse/WFLY-11492 > Project: WildFly > Issue Type: Bug > Components: Documentation, Security > Reporter: Alan Hantke > Assignee: Sonia Zaldana > Priority: Major > > Step #3, entitled *Configure the Application Security Domain* has the developer executing the following CLI command: > {code:java} > $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-security-domain.cli > {code} > However, this results in the following error: > {code:java} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): > WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed: > Step: step-1 > Operation: /subsystem=undertow/application-security-domain=other:add(http-authentication-factory=application-http-authentication) > Failure: WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.http-authentication-factory.application-http-authentication; Possible registration points for this capability: > /subsystem=elytron/http-authentication-factory=* > {code} > I am by no means an expert on this, but in looking at the standalone.xml file, I think that there needs to be a mate for the inserted *application-http-authentication*. I have attempted to continue without this changes installed by the CLI, but I am unable to execute the webapp even after providing the correct user/pass in the BASIC AUTH. > I have verified that the same problem-causing syntax exists on the quickstart 'master', although I have been using branch '14.x' because neither 15.x nor 'master' would build when I execute 'mvn clean build'. Finally, the I encounter the problem with fresh installs of WildFly versions 10.1.0 and 14.0. > Please change change the project if I have categorized the ticket incorrectly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 September 2020