April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1737) Clean up the 'wildfly-elytron-credential-store' module as it currently contains both public and private API

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1737?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1737: ---------------------------------- Fix Version/s: 1.9.0.CR4 (was: 1.9.0.CR3) > Clean up the 'wildfly-elytron-credential-store' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------------------- > > Key: ELY-1737 > URL: https://issues.jboss.org/browse/ELY-1737 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 1.9.0.CR4, 2.0.0.Alpha4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1766) Review relevence of webauth with Elytron authentication

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1766?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1766: ---------------------------------- Fix Version/s: 1.9.0.CR4 (was: 1.9.0.CR3) > Review relevence of webauth with Elytron authentication > ------------------------------------------------------- > > Key: ELY-1766 > URL: https://issues.jboss.org/browse/ELY-1766 > Project: WildFly Elytron > Issue Type: Task > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR4 > > > Does this just make sense in IDM / SSO environments or does it make sense for direct authentication to a server. > https://www.w3.org/TR/webauthn/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1765?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1765: ---------------------------------- Fix Version/s: 1.9.0.CR4 (was: 1.9.0.CR3) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.jboss.org/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.9.0.CR4 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1762) Ensure JAPICMP Compatibility and enable plug-in for all builds.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1762?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1762: ---------------------------------- Fix Version/s: 1.9.0.CR4 (was: 1.9.0.CR3) > Ensure JAPICMP Compatibility and enable plug-in for all builds. > --------------------------------------------------------------- > > Key: ELY-1762 > URL: https://issues.jboss.org/browse/ELY-1762 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.9.0.CR4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1749?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1749: ---------------------------------- Fix Version/s: 1.9.0.CR4 (was: 1.9.0.CR3) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.jboss.org/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR4 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Submarine version of Scesim editor

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3879: ---------------------------------------- Summary: Create Submarine version of Scesim editor Key: DROOLS-3879 URL: https://issues.jboss.org/browse/DROOLS-3879 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Create the *Submarine* (standalone) version of scesim editor -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3887) Smarter range validation error messages

by Michal Petrov (Jira)

[ https://issues.jboss.org/browse/WFCORE-3887?page=com.atlassian.jira.plugi... ] Michal Petrov resolved WFCORE-3887. ----------------------------------- Resolution: Out of Date Resolving as out of date, as far as I can determine this kind of message is not used in core or in WildFly proper. > Smarter range validation error messages > --------------------------------------- > > Key: WFCORE-3887 > URL: https://issues.jboss.org/browse/WFCORE-3887 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Michal Petrov > Priority: Minor > > A message like this is kind of silly: "Value must be between 0 and 9007199254740991". > Smarter would be the ParameterValidator code that detects the message checking if the range max is Integer.MAX_INT (for an int) or Long.MAX_LONG (for a long) and if the bad value is below the max, just saying the equivalent of "Value must be greater than %d". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11986) HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11986?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated WFLY-11986: ------------------------------------ Component/s: JCA (was: Application Client) (was: JPA / Hibernate) (was: Management) > HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11986 > URL: https://issues.jboss.org/browse/WFLY-11986 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 16.0.0.Final > Environment: Windows 10 Pro RU, MSSQL Server 2008 on remote machine, Microsoft JDBC driver. mssql-jdbc-6.2.2.jre7 > Reporter: Dmitry Lazarev > Assignee: Scott Marlow > Priority: Major > > When Datasource for MSSQL is created through HAL Management console, it inserts tag <datasource-class>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-class> in <datasource> element in standalone.xml. > Then when I try to test connection it fails with error "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid" If i remove element <datasource-class> manualy from standalone.xml, Test Connection works properly. > 2019-04-12 17:01:15,500 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (External Management Request Threads -- 2) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:1067) > at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:93) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:240) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:97) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.jboss.as.controller.ModelControllerImpl$$Lambda$489/1626912192.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/1133081806.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$541/1958155244.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$542/1328593333.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Не удалось установить соединение TCP/IP к серверу localhost по порту 1433. Ошибка: "Connection refused: no further information. Проверьте свойства соединения. Убедитесь, что на сервере запущен экземпляр SQL Server и он принимает TCP/IP-соединения по порту. Убедитесь, что TCP-соединения по этому порту не блокируются брандмауэром.". > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:227) > at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:284) > at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2435) > at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:635) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2010) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:968) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:78) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:314) > ... 39 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11986) HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11986?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-11986: --------------------------------------- Assignee: Stefano Maestri (was: Scott Marlow) > HAL Console places <datasource-class> in <datasource> element in standalone.xml. It leads to Test Connection fail > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11986 > URL: https://issues.jboss.org/browse/WFLY-11986 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 16.0.0.Final > Environment: Windows 10 Pro RU, MSSQL Server 2008 on remote machine, Microsoft JDBC driver. mssql-jdbc-6.2.2.jre7 > Reporter: Dmitry Lazarev > Assignee: Stefano Maestri > Priority: Major > > When Datasource for MSSQL is created through HAL Management console, it inserts tag <datasource-class>com.microsoft.sqlserver.jdbc.SQLServerDataSource</datasource-class> in <datasource> element in standalone.xml. > Then when I try to test connection it fails with error "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid" If i remove element <datasource-class> manualy from standalone.xml, Test Connection works properly. > 2019-04-12 17:01:15,500 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (External Management Request Threads -- 2) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:1067) > at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:93) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:240) > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:97) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.jboss.as.controller.ModelControllerImpl$$Lambda$489/1626912192.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$491/1133081806.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$541/1958155244.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$542/1328593333.run(Unknown Source) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Не удалось установить соединение TCP/IP к серверу localhost по порту 1433. Ошибка: "Connection refused: no further information. Проверьте свойства соединения. Убедитесь, что на сервере запущен экземпляр SQL Server и он принимает TCP/IP-соединения по порту. Убедитесь, что TCP-соединения по этому порту не блокируются брандмауэром.". > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:227) > at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:284) > at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2435) > at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:635) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2010) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:968) > at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnection(SQLServerDataSource.java:78) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:314) > ... 39 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1782) Update the branch for new features and enhancements in the "Contributions" section in the README.md

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1782?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1782: ------------------------------------- Assignee: Darran Lofthouse > Update the branch for new features and enhancements in the "Contributions" section in the README.md > --------------------------------------------------------------------------------------------------- > > Key: ELY-1782 > URL: https://issues.jboss.org/browse/ELY-1782 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR3 > > > The second sentence in the "Contributions" sections in the Elytron [README.md|https://github.com/wildfly-security/wildfly-elytron/blob/1.x/RE...] file currently says: > {quote} > All new features and enhancements should be submitted to master only. > {quote} > Since new features and enhancements should now be submitted against the 1.x branch instead of master, this sentence should be changed to: > {quote} > All new features and enhancements should be submitted to the 1.x branch only. > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019