[JBoss JIRA] (WFLY-7715) wildfly-service.exe and jbosspass wrong with # inside
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7715?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-7715:
--------------------------------------
Component/s: Scripts
Assignee: Tomaz Cerar (was: Jason Greene)
> wildfly-service.exe and jbosspass wrong with # inside
> -----------------------------------------------------
>
> Key: WFLY-7715
> URL: https://issues.jboss.org/browse/WFLY-7715
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Reporter: Seb Dk
> Assignee: Tomaz Cerar
>
> Hi there,
>
> I am installing wildfy 10.1.0 as service on a win 20012 server.
> It is working but I cannot stop the service.
> I figured out where the problem is coming from.
>
> When I installe Wildly as a service, I run the following command:
> E:\Products\wildfly-10.1.0.Final\bin\service>service.bat install /serviceuser .\JBoss /servicepass my#pass /controller localhost:9991 /jbossuser myuser /jbosspass *my#pass*
>
> But I can see whe I am trying to stop the service, the command running is:
> E:\Products\wildfly-10.1.0.Final\bin\jboss-cli.bat --controller=localhost:9991 --connect --user=myuser --password=*my" "pass* --command=:shutdown
>
> Any workaround?
>
> Thanks,
>
> S.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7587) Complicated failure-description for referral-mode in Elytron dir-context
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7587?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7587:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> Complicated failure-description for referral-mode in Elytron dir-context
> ------------------------------------------------------------------------
>
> Key: WFLY-7587
> URL: https://issues.jboss.org/browse/WFLY-7587
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
> Fix For: 11.0.0.Alpha1
>
>
> In case when attribute {{referral-mode}} is added to {{dir-context}} with wrong value then failure-description includes IllegalArgumentException instead of some non-Java admin friendly description:
> {code}
> /subsystem=elytron/dir-context=dirContext:add(url=localhost,referral-mode=abc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No enum constant org.wildfly.security.auth.realm.ldap.DirContextFactory.ReferralMode.abc",
> "rolled-back" => true
> }
> {code}
> Suggestion for improvement:
> Use the same type of failure-description as e.g. {{logical-role-mapper}}, see:
> {code}
> /subsystem=elytron/logical-role-mapper=logicalRoleMapper:add(logical-operation=abc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0248: Invalid value abc for logical-operation; legal values are [OR, AND, XOR, MINUS]",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7587) Complicated failure-description for referral-mode in Elytron dir-context
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7587?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7587:
-----------------------------------
Affects Version/s: (was: 11.0.0.Alpha1)
> Complicated failure-description for referral-mode in Elytron dir-context
> ------------------------------------------------------------------------
>
> Key: WFLY-7587
> URL: https://issues.jboss.org/browse/WFLY-7587
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
>
> In case when attribute {{referral-mode}} is added to {{dir-context}} with wrong value then failure-description includes IllegalArgumentException instead of some non-Java admin friendly description:
> {code}
> /subsystem=elytron/dir-context=dirContext:add(url=localhost,referral-mode=abc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No enum constant org.wildfly.security.auth.realm.ldap.DirContextFactory.ReferralMode.abc",
> "rolled-back" => true
> }
> {code}
> Suggestion for improvement:
> Use the same type of failure-description as e.g. {{logical-role-mapper}}, see:
> {code}
> /subsystem=elytron/logical-role-mapper=logicalRoleMapper:add(logical-operation=abc)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0248: Invalid value abc for logical-operation; legal values are [OR, AND, XOR, MINUS]",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2076) Wrong options for auto-completion in realms of Elytron security-domain in CLI
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2076?page=com.atlassian.jira.plugi... ]
Jan Kalina reassigned WFCORE-2076:
----------------------------------
Assignee: Brian Stansberry (was: Jan Kalina)
> Wrong options for auto-completion in realms of Elytron security-domain in CLI
> -----------------------------------------------------------------------------
>
> Key: WFCORE-2076
> URL: https://issues.jboss.org/browse/WFCORE-2076
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Server
> Affects Versions: 3.0.0.Alpha12
> Reporter: Ondrej Lukas
> Assignee: Brian Stansberry
> Labels: user_experience
>
> Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2076) Wrong options for auto-completion in realms of Elytron security-domain in CLI
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2076?page=com.atlassian.jira.plugi... ]
Jan Kalina moved WFLY-7586 to WFCORE-2076:
------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-2076 (was: WFLY-7586)
Component/s: Domain Management
Server
(was: Security)
Affects Version/s: 3.0.0.Alpha12
(was: 11.0.0.Alpha1)
> Wrong options for auto-completion in realms of Elytron security-domain in CLI
> -----------------------------------------------------------------------------
>
> Key: WFCORE-2076
> URL: https://issues.jboss.org/browse/WFCORE-2076
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Server
> Affects Versions: 3.0.0.Alpha12
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
>
> Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7586) Wrong options for auto-completion in realms of Elytron security-domain in CLI
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7586?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7586:
----------------------------------
Reproducible with upstream wildfly-core + elytron-subsystem (rest of wildfly or incubator versions of wildfly-core not needed).
Wrong output is sent as response to "suggest-capabilities" request - not CLI problem.
Problem is in CapabilityRegistry (wildfly-core/server) - getDynamicCapabilityNames():
* method is asked for security-realm capability (referencedCapability = "org.wildfly.security.security-realm")
* method filter two capabilities: "org.wildfly.security.security-realm.ldapName" and "org.wildfly.security.modifiable-security-realm.ldapName"
* method substring by length of referencedCapability (which cause "rity-realm.ldapName")
*The problem is, that CapabilityRegistry.getDynamicCapabilityNames() obtains all paths referring some realms and create matchers from them - later all matching capabilities are obtained - even through they are not referencedCapability - must be fixed in core.*
> Wrong options for auto-completion in realms of Elytron security-domain in CLI
> -----------------------------------------------------------------------------
>
> Key: WFLY-7586
> URL: https://issues.jboss.org/browse/WFLY-7586
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
>
> Auto-completion for realm in realms of security-domain provides wrong options. In case when ldap-realm with name ldapName is defined in configuration then also option {{rity-realm.ldapName}} occurs in auto-completion options. I am not able to reproduce this issue with properties-realm. Take a look at Steps to Reproduce for more details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7682) PropertiesSecurityRealm error handling
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7682?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7682:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> PropertiesSecurityRealm error handling
> --------------------------------------
>
> Key: WFLY-7682
> URL: https://issues.jboss.org/browse/WFLY-7682
> Project: WildFly
> Issue Type: Bug
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> Following exception is not enclosed into Realm exception when problem with properties file occure:
> {code:java}
> org.wildfly.security.util.DecodeException: ELY03007: Invalid hex character
> org.wildfly.security.util.NumericIterator$5.calc(NumericIterator.java:1074)
> org.wildfly.security.util.NumericIterator$5.hasNext(NumericIterator.java:1090)
> org.wildfly.security.util.ByteIterator.drainTo(ByteIterator.java:1153)
> org.wildfly.security.util.ByteIterator.drain(ByteIterator.java:1165)
> org.wildfly.security.auth.realm.LegacyPropertiesSecurityRealm$1.verifyEvidence(LegacyPropertiesSecurityRealm.java:171)
> org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1680)
> org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:655)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7716) Add tests for XA DataSource statistics
by Daniel Simko (JIRA)
[ https://issues.jboss.org/browse/WFLY-7716?page=com.atlassian.jira.plugin.... ]
Daniel Simko updated WFLY-7716:
-------------------------------
Description: Add new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount). (was: Added new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount).)
> Add tests for XA DataSource statistics
> --------------------------------------
>
> Key: WFLY-7716
> URL: https://issues.jboss.org/browse/WFLY-7716
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Daniel Simko
> Assignee: Daniel Simko
> Priority: Minor
>
> Add new testcase for testing xa-data-source's pool statistics (XACommitCount, XARollbackCount, XAStartCount).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month