March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-466) Add a GSSCredential CredentialStore

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-466: ------------------------------------ Summary: Add a GSSCredential CredentialStore Key: ELY-466 URL: https://issues.jboss.org/browse/ELY-466 Project: WildFly Elytron Issue Type: Feature Request Components: Credential Store Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 This will be used to provide GSSCredential instances for use by authentication mechanisms. Ideally a single store can support multiple credentials, the alias paramater may be a good way to map from the host name of the request to the ticket to use. Need to think how much this makes sense to load using the Provider as it could potentially have quite a verbose configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1066) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1066?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-1066: ---------------------------------------- Contributions are of course welcome. I interpreted your previous question as a request that we shift our own resources to this. I'm not going to lie to you and tell you sure, we'll do that, when the reality is I have no idea if I'll have the available resources. I'm quite certain doing this any time in the next year will mean we defer some other requests from PM. PM approving work in community has nothing to do with this. > Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING) > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1066 > URL: https://issues.jboss.org/browse/WFLY-1066 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: Server running in Domain mode > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Labels: clustering, domain, jgroups > > It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode. > All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration. > The domain server will receive the informations if a host-controller enrol and register server to a clustered server-group. > So the configuration of the initial_hosts can be done automaticaly to avoid old entries which cause unnecessary checks and ensure that all active servers are known. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-443) Update KeyStore backed security realm to iterate it's entries to attempt to find a matching alias for the evidence.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-443?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-443: -------------------------------------- Stopping progress for now, if the following PR is merged this change should not be required as the Principal will automatically be set: - https://github.com/wildfly-security/wildfly-elytron/pull/389 > Update KeyStore backed security realm to iterate it's entries to attempt to find a matching alias for the evidence. > ------------------------------------------------------------------------------------------------------------------- > > Key: ELY-443 > URL: https://issues.jboss.org/browse/ELY-443 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Ideally an EvidenceDecoder would have been used up front but as this is technically possible to implement we should do so. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1029) ManagedSocketFactory doesn't work for client sockets

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1029?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1029: ---------------------------------------- Assignee: Brian Stansberry Resolution: Done > ManagedSocketFactory doesn't work for client sockets > ---------------------------------------------------- > > Key: WFCORE-1029 > URL: https://issues.jboss.org/browse/WFCORE-1029 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR5 > Reporter: Dennis Reed > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha1 > > > SocketBindingManagerImpl does not work with client sockets. > It adds sockets to a map based on local address. Client sockets that have not been bound yet do not have a local address. > This breaks the JGroups subsystem's ManagedSocketFactory, which uses SocketBindingManagerImpl for both server and client sockets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy... ] Pedro Igor commented on ELY-428: -------------------------------- Ok. Notes now updated :) > HTTP Mechanism configuration during deployment > ---------------------------------------------- > > Key: ELY-428 > URL: https://issues.jboss.org/browse/ELY-428 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta5 > > > It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application. > The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1112) ModuleSpecProcessor not necessary char allocation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1112?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1112: ---------------------------------------- Assignee: Vladimir Gordiychuk (was: Jason Greene) > ModuleSpecProcessor not necessary char allocation > ------------------------------------------------- > > Key: WFCORE-1112 > URL: https://issues.jboss.org/browse/WFCORE-1112 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Vladimir Gordiychuk > Assignee: Vladimir Gordiychuk > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > [org.jboss.as.server.deployment.module.ModuleSpecProcessor|https://github....] concatenate string for debug logging without check that log level debug available or not, as result we allocate annesesary char[] during start server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1068) Simplify failing in the case of RBAC AuthorizationResult.Decision.DENY

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1068?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1068: ---------------------------------------- Assignee: Brian Stansberry Resolution: Done > Simplify failing in the case of RBAC AuthorizationResult.Decision.DENY > ---------------------------------------------------------------------- > > Key: WFCORE-1068 > URL: https://issues.jboss.org/browse/WFCORE-1068 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Optional > Fix For: 3.0.0.Alpha1 > > > There's a fair amount of this kind of code in misc OSHs that directly ask the OperationContext to authorize something: > {code} > AuthorizationResult authorizationResult = context.authorize(...); > if (authorizationResult.getDecision() == AuthorizationResult.Decision.DENY) { > throw ControllerMessages.MESSAGES.unauthorized(operation.get(OP).asString(), > context.getCurrentAddress()), authorizationResult.getExplanation()); > } > {code} > We can replace that if block with a call to a new util method on AuthorizationResult itself: > {code} > public void failIfDenied(ModelNode operation, PathAddress pathAddress) throws OperationFailedException > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2032) TOA logs too much at DEBUG level

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2032?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2032. ---------------------------- Resolution: Done > TOA logs too much at DEBUG level > -------------------------------- > > Key: JGRP-2032 > URL: https://issues.jboss.org/browse/JGRP-2032 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.8 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.9, 4.0 > > > Sent/delivered messages should only be logged at TRACE level, not DEBUG. > Exceptions should be logged at WARN level (or maybe ERROR), regardless of the current logging level. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-428: -------------------------------------- HttpServerAuthenticationMechanismFactory will be able to do that if it has the configuration - the place it does not have this is where this is a deployment which is why we need a deployer to handle that. > HTTP Mechanism configuration during deployment > ---------------------------------------------- > > Key: ELY-428 > URL: https://issues.jboss.org/browse/ELY-428 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta5 > > > It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application. > The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-465) On ServerAuthenticationContext allow getCredentialAcquireSupport and getEvidenceVerifySupport to query the domain if the realm and identity is not known

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-465: ------------------------------------ Summary: On ServerAuthenticationContext allow getCredentialAcquireSupport and getEvidenceVerifySupport to query the domain if the realm and identity is not known Key: ELY-465 URL: https://issues.jboss.org/browse/ELY-465 Project: WildFly Elytron Issue Type: Feature Request Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 The purpose of our SupportLevel approach is the certainty of the response has the potential to become more accurate the more we know - if we don't know enough we should be able to obtain the general response from the domain or possibly from the realm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016