[JBoss JIRA] (WFLY-2248) Upgrade to JBoss SASL 1.0.4.CR1
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-2248:
--------------------------------------
Summary: Upgrade to JBoss SASL 1.0.4.CR1
Key: WFLY-2248
URL: https://issues.jboss.org/browse/WFLY-2248
Project: WildFly
Issue Type: Component Upgrade
Components: Domain Management, Remoting, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 8.0.0.CR1
To allow relaxing the protocol check within the Digest MD5 mechanism.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-2247) Add javax.transaction.api to JDBC module
by Jesper Pedersen (JIRA)
Jesper Pedersen created WFLY-2247:
-------------------------------------
Summary: Add javax.transaction.api to JDBC module
Key: WFLY-2247
URL: https://issues.jboss.org/browse/WFLY-2247
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 8.0.0.Beta1
Reporter: Jesper Pedersen
Assignee: Stefano Maestri
Fix For: 8.0.0.CR1
Add the javax.transaction.api module to the JDBC module such that people can use XA related classes during verification
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (WFLY-1592) Attempting to use eap6.1 jboss-cli.sh to connect to remote wildfly (alpha1 or 2) fails; credentials not accepted
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1592?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-1592:
----------------------------------------
This issue is due to changes introduced in REM3-29 where the default protocol was switched from 'remote' to 'remoting'.
Reverting that change would not be appropriate as it is needed to be able to enable GSSAPI support.
The change for REM3-29 does allow the protocol name to be specified in configuration however doing that would require the same config on the server and in all clients - it would also only be a short term fix until we enable support for GSSAP.
SASL-42 will instead allow the server side to specify a list of accepted alternative protocols, when GSSAPI is in use it will be essential for clients using it to use the correct protocol but older clients may still want to connect with username / password auth.
> Attempting to use eap6.1 jboss-cli.sh to connect to remote wildfly (alpha1 or 2) fails; credentials not accepted
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-1592
> URL: https://issues.jboss.org/browse/WFLY-1592
> Project: WildFly
> Issue Type: Bug
> Components: Remoting, Security
> Affects Versions: 8.0.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> Using eap6.1 client jars, or the jboss-cli.sh script in a local eap6.1 installation, to connect to a remote wildfly alpha1 or alpha2, seems to work but fails when provided with credentials. This is most easily replicated as follows:
> 1) On remote machine start wildfly alpha1 or alpha2
> 2) on local machine, cd eap-6.1/bin
> 3) on local machine:
> [rob@rawbdor bin]$ ./jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] connect myhost.net
> Authenticating against security realm: ManagementRealm
> Username: admin
> Password:
> Unable to authenticate against controller at myhost.net:9999: Authentication failed: all available authentication mechanisms failed
> This is an issue for tools as we need a set of jars that communicates correctly with all as7 servers. We currently have a set of jars that communicates with all 7.x / eap 6.x, which is good. If this is merely a bug on the server, then we can hopefully delay having to bundle an additional set of client jars until larger breakages occur.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (SASL-42) Add option to relax protocol check within mechanisms.
by Darran Lofthouse (JIRA)
Darran Lofthouse created SASL-42:
------------------------------------
Summary: Add option to relax protocol check within mechanisms.
Key: SASL-42
URL: https://issues.jboss.org/browse/SASL-42
Project: JBoss SASL Provider
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.4.CR1
The Digest MD5 mechanism contains a check that the URI received from the remote client matches the expected value, unfortunately older clients use a hard coded protocol or 'remote' - newer clients and servers use 'remoting'.
This issue is to add a configuration option so that server side this checking can be relaxed, most appropriate would be to supply a list of accepted alternative protocols.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months