October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-257) Allow usage of properties to configure sasl server factories

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-257?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-257: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Allow usage of properties to configure sasl server factories > ------------------------------------------------------------ > > Key: ELY-257 > URL: https://issues.jboss.org/browse/ELY-257 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta3 > > > There is some discussion on https://github.com/wildfly-security/wildfly-elytron/pull/264. In this case the issue is that we have a ChannelBindingSaslServerFactory (and same for client) which provides a callback handler to deal with the channel binding callbacks needed by Gs2SaslServerFactory and Gs2SaslClientFactory. This is fine for when people create their own SaslServerFactory, and use that to create a SaslServer. > However, if they want to call Sasl.createServer()/.createClient() they need to provide their own callback handler to deal with the channel binding types. > One option would be to allow the usage of properties for this configuration needed by the factories. > However, having slept on it, the callback handler passed in to Sasl.createXXX() would need to handle all callbacks. Is there a way to get a 'real' callback handler for a user wishing to instantiate clients/servers this way? Or is the intent that they have to write their own CBH? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-261: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Rework (and move) UsernamePasswordHashUtil > ------------------------------------------ > > Key: ELY-261 > URL: https://issues.jboss.org/browse/ELY-261 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI, Passwords > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > Firstly this class is not really SASL specific so should be in a general util package. > Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-258) Inconsistent 'AuthenticationContext' naming.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-258?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-258: --------------------------------- Priority: Critical (was: Major) > Inconsistent 'AuthenticationContext' naming. > -------------------------------------------- > > Key: ELY-258 > URL: https://issues.jboss.org/browse/ELY-258 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta2 > > > Other classes in these packages should also be checked but essentially we have a client and server package, the context in client is AuthenticationContext, the one in server is ServerAuthenticationContext. > If they are ever likely to be both used together then unique names would be advisable, otherwise they could both be 'AuthenticationContext'. > Wait till all engineers are off PTO before working on this one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-279) Support CORS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-279?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-279: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Support CORS > ------------ > > Key: ELY-279 > URL: https://issues.jboss.org/browse/ELY-279 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > This is something that can possibly be tied in around the HTTP authentication framework meaning that the control of this can live in the HTTP authentication policy within Elytron rather than at the front end. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-298: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > load-from/uri keystore xsd/parser mismatch > ------------------------------------------ > > Key: ELY-298 > URL: https://issues.jboss.org/browse/ELY-298 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > The xsd has > {code} > <xsd:complexType name="key-store-type"> > <xsd:sequence minOccurs="1" maxOccurs="1"> >  > <xsd:choice minOccurs="1" maxOccurs="1"> > <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/> > <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/> > {code} > The parser seems to look for 'uri' rather than 'load-from' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-295) Custom CredentialMapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-295?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-295. ---------------------------------- Assignee: Darran Lofthouse Resolution: Out of Date > Custom CredentialMapper > ----------------------- > > Key: ELY-295 > URL: https://issues.jboss.org/browse/ELY-295 > Project: WildFly Elytron > Issue Type: Task > Components: Passwords > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta2 > > > We will need to review if this is actually required - however with credentials now being query-able by String we may want to support overriding the mappings used by the CredentialMapper either for custom mechanisms or custom realms. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-293) Add file based auth to http management interface

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-293?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-293: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Add file based auth to http management interface > ------------------------------------------------ > > Key: ELY-293 > URL: https://issues.jboss.org/browse/ELY-293 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Max Rydahl Andersen > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > 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 was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-347) Rework all realm implementations that use credential names

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-347?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-347: ------------------------------------ Assignee: Darran Lofthouse > Rework all realm implementations that use credential names > ---------------------------------------------------------- > > Key: ELY-347 > URL: https://issues.jboss.org/browse/ELY-347 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta2 > > > A number of the realm implementations are making use of credential names - for the ones that are not automatic we need to ensure they are configurable instead as within Elytron we no longer need a set of standard names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-344) Review how clients use ModifiableRealmIdentity / ModifiableRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-344?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-344: --------------------------------- Fix Version/s: 1.1.0.Beta3 (was: 1.1.0.Beta2) > Review how clients use ModifiableRealmIdentity / ModifiableRealm > ---------------------------------------------------------------- > > Key: ELY-344 > URL: https://issues.jboss.org/browse/ELY-344 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta3 > > > This may be something we address in the subsystem but just raising here so we don't forget. > Once we have a working set up with a realm which can be modified it seems unreasonable to expect the administrator to know exactly which credential types and names to use. > This may need to be a few milestones away once we have the bulk integrated so the relationships are clear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-30) Support automatic log file compression in FileHandler (for compressing all files in real time) and PeriodicRotatingFileHandler (for compressing upon rotation)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-30?page=com.atlassian.jira.plugin.... ] James Perkins reassigned LOGMGR-30: ----------------------------------- Assignee: James Perkins > Support automatic log file compression in FileHandler (for compressing all files in real time) and PeriodicRotatingFileHandler (for compressing upon rotation) > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: LOGMGR-30 > URL: https://issues.jboss.org/browse/LOGMGR-30 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: Aleksander Adamowski > Assignee: James Perkins > Fix For: 2.1.0.Beta1 > > > This is a follow up to JBAS-6917. > It would be nice to have an automatic compression of log files similar to the one implemented in Log4j extras: > http://logging.apache.org/log4j/companions/extras/apidocs/org/apache/log4... > "TimeBasedRollingPolicy supports automatic file compression. This feature is enabled if the value of the FileNamePattern option ends with .gz or .zip." > In JBoss Logging, I suppose this could be implemented on 2 levels: > 1) In the FileHandler (http://anonsvn.jboss.org/repos/common/jboss-logmanager/trunk/src/main/jav...) so that, with proper configuration, each log file is compressed in real time, and it exists only in compressed form from the moment of its creation. > 2) In the PeriodicRotatingFileHandler (http://anonsvn.jboss.org/repos/common/jboss-logmanager/trunk/src/main/jav...) so that with proper configuration, archival log files can be compressed the moment they are rotated (e.g. server.log.2010-05-06.gz is created instead of server.log.2010-05-06), but the current log file should be plain text. > In PeriodicRotatingFileHandler, the implementation must take into account that compression of rotated log files may take considerable time and should be performed in the background - the handler should be able to process log records at any time, particularly during rotation, without losing any. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 October 2015