[JBoss JIRA] (WFCORE-2827) undefined suffix in rotating-file-audit-log not handled
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2827?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2827:
-------------------------------
Steps to Reproduce:
Try to add following audit log:
{code}
/subsystem=elytron/rotating-file-audit-log=myAppRotate/:add(path=audit.log,format=SIMPLE,max-backup-index=1,rotate-on-boot=false,rotate-size=2000,synchronized=true,relative-to=jboss.server.log.dir)
{code}
Creating will fail.
was:
{code}
/subsystem=elytron/rotating-file-audit-log=myAppRotate/:add(path=audit.log,format=SIMPLE,max-backup-index=1,rotate-on-boot=false,rotate-size=2000,synchronized=true,relative-to=jboss.server.log.dir)
{code}
> undefined suffix in rotating-file-audit-log not handled
> -------------------------------------------------------
>
> Key: WFCORE-2827
> URL: https://issues.jboss.org/browse/WFCORE-2827
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta21
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> Attribute *suffix* of *rotating-file-audit-log* is optional, but if not filled, following exception occure:
> {code}
> MSC000001: Failed to start service org.wildfly.security.security-event-listener.myAppRotate: org.jboss.msc.service.StartException in service org.wildfly.security.security-event-listener.myAppRotate: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'
> at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
> at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
> at org.wildfly.security.audit.RotatingFileAuditEndpoint$Builder.setSuffix(RotatingFileAuditEndpoint.java:289)
> at org.wildfly.extension.elytron.AuditResourceDefinitions$2.lambda$getValueSupplier$2(AuditResourceDefinitions.java:247)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2827) undefined suffix in rotating-file-audit-log not handled
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2827?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2827:
-------------------------------
Priority: Critical (was: Major)
> undefined suffix in rotating-file-audit-log not handled
> -------------------------------------------------------
>
> Key: WFCORE-2827
> URL: https://issues.jboss.org/browse/WFCORE-2827
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta21
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> Attribute *suffix* of *rotating-file-audit-log* is optional, but if not filled, following exception occure:
> {code}
> MSC000001: Failed to start service org.wildfly.security.security-event-listener.myAppRotate: org.jboss.msc.service.StartException in service org.wildfly.security.security-event-listener.myAppRotate: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'
> at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
> at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
> at org.wildfly.security.audit.RotatingFileAuditEndpoint$Builder.setSuffix(RotatingFileAuditEndpoint.java:289)
> at org.wildfly.extension.elytron.AuditResourceDefinitions$2.lambda$getValueSupplier$2(AuditResourceDefinitions.java:247)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2827) undefined suffix in rotating-file-audit-log not handled
by Jan Kalina (JIRA)
Jan Kalina created WFCORE-2827:
----------------------------------
Summary: undefined suffix in rotating-file-audit-log not handled
Key: WFCORE-2827
URL: https://issues.jboss.org/browse/WFCORE-2827
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.0.Beta21
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
Attribute *suffix* of *rotating-file-audit-log* is optional, but if not filled, following exception occure:
{code}
MSC000001: Failed to start service org.wildfly.security.security-event-listener.myAppRotate: org.jboss.msc.service.StartException in service org.wildfly.security.security-event-listener.myAppRotate: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'
at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
at org.wildfly.security.audit.RotatingFileAuditEndpoint$Builder.setSuffix(RotatingFileAuditEndpoint.java:289)
at org.wildfly.extension.elytron.AuditResourceDefinitions$2.lambda$getValueSupplier$2(AuditResourceDefinitions.java:247)
at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2827) undefined suffix in rotating-file-audit-log not handled
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2827?page=com.atlassian.jira.plugi... ]
Jan Kalina updated WFCORE-2827:
-------------------------------
Priority: Major (was: Critical)
> undefined suffix in rotating-file-audit-log not handled
> -------------------------------------------------------
>
> Key: WFCORE-2827
> URL: https://issues.jboss.org/browse/WFCORE-2827
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta21
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Attribute *suffix* of *rotating-file-audit-log* is optional, but if not filled, following exception occure:
> {code}
> MSC000001: Failed to start service org.wildfly.security.security-event-listener.myAppRotate: org.jboss.msc.service.StartException in service org.wildfly.security.security-event-listener.myAppRotate: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'n'
> at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
> at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
> at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
> at org.wildfly.security.audit.RotatingFileAuditEndpoint$Builder.setSuffix(RotatingFileAuditEndpoint.java:289)
> at org.wildfly.extension.elytron.AuditResourceDefinitions$2.lambda$getValueSupplier$2(AuditResourceDefinitions.java:247)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1080) Allow authorization identity to be specified as a Principal
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-1080?page=com.atlassian.jira.plugin.s... ]
David Lloyd resolved ELY-1080.
------------------------------
Fix Version/s: 1.1.0.Beta37
(was: 1.1.0.Beta44)
Resolution: Done
> Allow authorization identity to be specified as a Principal
> -----------------------------------------------------------
>
> Key: ELY-1080
> URL: https://issues.jboss.org/browse/ELY-1080
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta37
>
>
> The authorization identity is the identity that the user intends to run as. By allowing the identity to be specified as a Principal, the anonymous identity can be given, which is a way of directly selecting anonymous authentication. The existing methods which specify the authorization identity as a string can map to a NamePrincipal. Mechanism selection can also take the authorization ID into account.
> This also aligns with the run-as logic on the server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (REMJMX-138) Allow a URI for the Elytron configuration to be passed to environment when establishing a connection
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-138?page=com.atlassian.jira.plugin... ]
Darran Lofthouse resolved REMJMX-138.
-------------------------------------
Resolution: Done
> Allow a URI for the Elytron configuration to be passed to environment when establishing a connection
> ----------------------------------------------------------------------------------------------------
>
> Key: REMJMX-138
> URL: https://issues.jboss.org/browse/REMJMX-138
> Project: Remoting JMX
> Issue Type: Enhancement
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 3.0.0.Beta4
>
>
> Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.url}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one.
> This is more of a nice to have for clients so they do not need to be aware of using Elytron directly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (REMJMX-138) Allow a URI for the Elytron configuration to be passed to environment when establishing a connection
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/REMJMX-138?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated REMJMX-138:
------------------------------------
Fix Version/s: 3.0.0.Beta4
> Allow a URI for the Elytron configuration to be passed to environment when establishing a connection
> ----------------------------------------------------------------------------------------------------
>
> Key: REMJMX-138
> URL: https://issues.jboss.org/browse/REMJMX-138
> Project: Remoting JMX
> Issue Type: Enhancement
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 3.0.0.Beta4
>
>
> Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.url}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one.
> This is more of a nice to have for clients so they do not need to be aware of using Elytron directly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month