November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-711) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-711?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-711: ------------------------------ Assignee: Jan Kalina Resolution: Done > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-711 > URL: https://issues.jboss.org/browse/ELY-711 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Choma > Assignee: Jan Kalina > > Basically Elytron clone of JBEAP-4114. > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-711) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-711?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved WFLY-7397 to ELY-711: -------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-711 (was: WFLY-7397) Component/s: Authentication Mechanisms (was: Security) Affects Version/s: (was: 11.0.0.Alpha1) > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-711 > URL: https://issues.jboss.org/browse/ELY-711 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Choma > > Basically Elytron clone of JBEAP-4114. > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-710) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-710?page=com.atlassian.jira.plugin.sy... ] Jan Kalina deleted ELY-710: --------------------------- > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-710 > URL: https://issues.jboss.org/browse/ELY-710 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Jan Kalina > Assignee: Jan Kalina > > Basically Elytron clone of JBEAP-4114. > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-710) Elytron SPNEGO: missing negstat field in the first reply

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-710?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved JBEAP-6819 to ELY-710: --------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-710 (was: JBEAP-6819) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Authentication Mechanisms (was: Security) Affects Version/s: (was: 7.1.0.DR7) > Elytron SPNEGO: missing negstat field in the first reply > -------------------------------------------------------- > > Key: ELY-710 > URL: https://issues.jboss.org/browse/ELY-710 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Jan Kalina > Assignee: Jan Kalina > > Basically Elytron clone of JBEAP-4114. > When the client sends an initial SPNEGO token with Kerberos as preferred mechanism and includes an invalid kerberos token, then client expects to see the {{WWW-Authenticate}} HTTP header with SPNEGO response {{negTokenResp[ negState = reject ]}}. > As stated in [SPNEGO specification|https://tools.ietf.org/html/rfc4178#section-4.2.2] negstat is required in first reply: > {code:borderStyle=dashed} > negState > ... > This field is REQUIRED in the first reply from the target, and is > OPTIONAL thereafter. When negState is absent, the actual state > should be inferred from the state of the negotiated mechanism > context. > {code} > https://github.com/wildfly/wildfly/blob/15f9a4f2b5a10cc3acbaa2df57d5cc13d... testInvalidKerberosSpnegoWorkflow. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1921) Problem with capability-reference to resource whose name is number with ZERO(s) prefix.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1921?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1921: ---------------------------------------- Component/s: Domain Management (was: CLI) Assignee: Tomaz Cerar (was: Jean-Francois Denise) I'm changing the component as the reproducer steps show nothing related to the client. [~ctomc], please correct the component and assignee on the linked JBEAP as well. The fact that datasources also show a problem leads me to pick Domain Management instead of the security subsystem component. BTW, in the reproducer steps "/subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper" looks like a typo, with the 001 in the address element key rather than the value. I assume the problem is still reproducible with that corrected though, as the failure message is unrelated to a bad resource address and the datasource example also given doesn't have that problem. > Problem with capability-reference to resource whose name is number with ZERO(s) prefix. > --------------------------------------------------------------------------------------- > > Key: WFCORE-1921 > URL: https://issues.jboss.org/browse/WFCORE-1921 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Hynek Švábek > Assignee: Tomaz Cerar > > Problem with resources which name contains only NUMBERS. > Particularly the number which beginning with ZERO(s). > *Scenario* > * I have resources which name contains only numbers with ZERO(s) prefix > * I want set capability-reference to it > * e.g. /subsystem=elytron/aggregate-role-mapper001=aggregateRoleMapper:add(role-mappers=[001,111]) > *Actual result* > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0369: Required capabilities are not available: > org.wildfly.security.role-mapper.1; There are no known registration points which can provide this capability.", > "rolled-back" => true > } > {code} > *Expected result* > {code} > Success > {code} > *NOTE* > In my opinion is this global problem. > I tried it with another subsystem and problem is there too. > {code} > /subsystem=datasources/data-source=001:add(connection-url="url", jndi-name="java:jboss/datasources/001", driver-name=h2) > /subsystem=infinispan/cache-container=server/local-cache=default/store=string-jdbc:add(data-source=001) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7456) Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself

by Radim Hatlapatka (JIRA)

Radim Hatlapatka created WFLY-7456: -------------------------------------- Summary: Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself Key: WFLY-7456 URL: https://issues.jboss.org/browse/WFLY-7456 Project: WildFly Issue Type: Bug Components: Mail Reporter: Radim Hatlapatka Assignee: Tomaz Cerar Priority: Optional There is inconsistent description for custom server when reading it as child description => {{/subsystem=mail/mail-session=default:read-resource-description}}, where it is {{Custom mail server configuration}} and when reading its description directly => {{/subsystem=mail/mail-session=default/custom=xxx:read-resource-description}}, where it is {{Mail session server}} This doesn't look nice from UX PoV, where I believe these values should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7456) Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-7456?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka updated WFLY-7456: ----------------------------------- Affects Version/s: 10.1.0.Final > Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7456 > URL: https://issues.jboss.org/browse/WFLY-7456 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 10.1.0.Final > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > Priority: Optional > Labels: user_experience > > There is inconsistent description for custom server when reading it as child description => {{/subsystem=mail/mail-session=default:read-resource-description}}, where it is {{Custom mail server configuration}} and when reading its description directly => {{/subsystem=mail/mail-session=default/custom=xxx:read-resource-description}}, where it is {{Mail session server}} > This doesn't look nice from UX PoV, where I believe these values should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7456) Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself

by Radim Hatlapatka (JIRA)

[ https://issues.jboss.org/browse/WFLY-7456?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka updated WFLY-7456: ----------------------------------- Labels: user_experience (was: ) > Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7456 > URL: https://issues.jboss.org/browse/WFLY-7456 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 10.1.0.Final > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > Priority: Optional > Labels: user_experience > > There is inconsistent description for custom server when reading it as child description => {{/subsystem=mail/mail-session=default:read-resource-description}}, where it is {{Custom mail server configuration}} and when reading its description directly => {{/subsystem=mail/mail-session=default/custom=xxx:read-resource-description}}, where it is {{Mail session server}} > This doesn't look nice from UX PoV, where I believe these values should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7388) NullPointerException Adding FileSystemRealm with identities in a batch.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7388?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7388: ---------------------------------- [~brian.stansberry] The spaces in --commands are escaped - the argument continues - it is equivalent of: *--commands="embed-server --server-config=standalone-elytron.xml,run-batch --file=/opt/jboss/commands.txt,stop-embedded-server"* > NullPointerException Adding FileSystemRealm with identities in a batch. > ----------------------------------------------------------------------- > > Key: WFLY-7388 > URL: https://issues.jboss.org/browse/WFLY-7388 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > {code:java} > /subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper) > {code} > {noformat} > Step 21 : RUN /opt/jboss/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/bin/jboss-cli.sh --commands=embed-server\ --server-config=standalone-elytron.xml,run-batch\ --file=/opt/jboss/commands.txt,stop-embedded-server > ---> Running in fb3e83746136 > The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} > {noformat} > NullPointerException experienced randomly, initially this sounds like the service is not fully up by the time the first command completes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7388) NullPointerException Adding FileSystemRealm with identities in a batch.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7388?page=com.atlassian.jira.plugin.... ] Jan Kalina edited comment on WFLY-7388 at 11/2/16 9:48 AM: ----------------------------------------------------------- [~brian.stansberry] The spaces in --commands are escaped - the argument continues - it is equivalent of: {code:java} --commands="embed-server --server-config=standalone-elytron.xml,run-batch --file=/opt/jboss/commands.txt,stop-embedded-server" {code} was (Author: honza889): [~brian.stansberry] The spaces in --commands are escaped - the argument continues - it is equivalent of: *--commands="embed-server --server-config=standalone-elytron.xml,run-batch --file=/opt/jboss/commands.txt,stop-embedded-server"* > NullPointerException Adding FileSystemRealm with identities in a batch. > ----------------------------------------------------------------------- > > Key: WFLY-7388 > URL: https://issues.jboss.org/browse/WFLY-7388 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > {code:java} > /subsystem=elytron/filesystem-realm=exampleFsRealm:add(path=fs-realm-users,relative-to=jboss.server.config.dir) > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add() > /subsystem=elytron/filesystem-realm=exampleFsRealm/identity=jduke@JBOSS.ORG:add-attribute(name=Roles, value=["Admin","Guest"]) > /subsystem=elytron/simple-role-decoder=from-roles-attribute:add(attribute=Roles) > /subsystem=elytron/security-domain=exampleFsSD:add(realms=[{realm=exampleFsRealm,role-decoder=from-roles-attribute}],default-realm=exampleFsRealm,permission-mapper=login-permission-mapper) > {code} > {noformat} > Step 21 : RUN /opt/jboss/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/bin/jboss-cli.sh --commands=embed-server\ --server-config=standalone-elytron.xml,run-batch\ --file=/opt/jboss/commands.txt,stop-embedded-server > ---> Running in fb3e83746136 > The batch failed with the following error: : {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException"}} > {noformat} > NullPointerException experienced randomly, initially this sounds like the service is not fully up by the time the first command completes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016