[JBoss JIRA] (WFCORE-2640) Improve description of Elytron mapped-regex-realm-mapper and simple-regex-realm-mapper
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2640?page=com.atlassian.jira.plugi... ]
Ondrej Lukas updated WFCORE-2640:
---------------------------------
Labels: user_experience (was: )
> Improve description of Elytron mapped-regex-realm-mapper and simple-regex-realm-mapper
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-2640
> URL: https://issues.jboss.org/browse/WFCORE-2640
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> Description of Elytron {{mapped-regex-realm-mapper}} and {{simple-regex-realm-mapper}} for {{read-resource-description}} operation in JBoss CLI and in {{wildfly-elytron_1_0.xsd}} should be improved. Following information should be provided there for {{mapped-regex-realm-mapper}}:
> * In case when username does not matches pattern and delegate-realm-mapper is used then result of delegate-realm-mapper is mapped through realm-map. Add this information to description of {{delegate-realm-mapper}}.
> * In case when value for mapping is not in the map or in case when realm with name of value in {{to}} from realm-map does exist in given security domain then default realm is used.
> Following information should be provided for both {{simple-regex-realm-mapper}} and {{mapped-regex-realm-mapper}}
> * In case when more capture groups are obtained in pattern then first capture group is used. Add this information to description of {{pattern}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8532) Create test cases for Elytron Realm Mappers
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-8532:
----------------------------------
Summary: Create test cases for Elytron Realm Mappers
Key: WFLY-8532
URL: https://issues.jboss.org/browse/WFLY-8532
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Ondrej Lukas
Assignee: Ondrej Lukas
Create test cases for following Elytron Realm Mappers:
* constant-realm-mapper
* simple-regex-realm-mapper
* mapped-regex-realm-mapper
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7192) 'name' attribute missing in XSD while required by web subsystem parser
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-7192?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-7192:
-----------------------------------------------
Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1365939|https://bugzilla.redhat.com/show_bug.cgi?id=1365939] from MODIFIED to ON_QA
> 'name' attribute missing in XSD while required by web subsystem parser
> ----------------------------------------------------------------------
>
> Key: WFLY-7192
> URL: https://issues.jboss.org/browse/WFLY-7192
> Project: WildFly
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Labels: downstream_dependency
> Fix For: 11.0.0.Alpha1
>
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1365939 , originaly reported by [~paramjindal]
> While configuring the global valve using the following article :
> https://access.redhat.com/solutions/379813
> It is mandatory that the "name" attribute of valve must match the "auth-method" that is specified in the "WEB-INF/web.xml".
> So "name" attribute is mandatory to configure this valve.
> but it is not mentioned in the schema of valve as shown below :
> {code:xml}
> <xs:element name="valve">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="param" minOccurs="0" maxOccurs="unbounded" type="paramType" />
> </xs:sequence>
> <xs:attribute name="class-name" type="xs:string" use="required" />
> <xs:attribute name="module" type="xs:string" use="required" />
> <xs:attribute name="enabled" default="true" type="xs:boolean" />
> </xs:complexType>
> </xs:element>
> {code}
> Version-Release number of selected component (if applicable):
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2639) Elytron server-ssl-context does not work with key manager exported from legacy security domain
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2639?page=com.atlassian.jira.plugi... ]
Ondrej Kotek moved JBEAP-10192 to WFCORE-2639:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2639 (was: JBEAP-10192)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 3.0.0.Beta13
(was: 7.1.0.DR16)
> Elytron server-ssl-context does not work with key manager exported from legacy security domain
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-2639
> URL: https://issues.jboss.org/browse/WFCORE-2639
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta13
> Reporter: Ondrej Kotek
> Priority: Critical
> Labels: legacy-integration
>
> Elytron {{server-ssl-context}} does not work with key manager exported from legacy security domain. A connection is refused.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8530) Wrong ZonedDateTime value read when attribute annotated with @Id
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-8530?page=com.atlassian.jira.plugin.... ]
Jörg Bäsner updated WFLY-8530:
------------------------------
Steps to Reproduce:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: *2017-10-29T02:00+02:00[Europe/Berlin]*, withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: *2017-10-29T02:00+01:00[Europe/Berlin]*, offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
was:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
{{10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: *2017-10-29T02:00+02:00[Europe/Berlin]*, withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: *2017-10-29T02:00+01:00[Europe/Berlin]*, offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------}}
> Wrong ZonedDateTime value read when attribute annotated with @Id
> ----------------------------------------------------------------
>
> Key: WFLY-8530
> URL: https://issues.jboss.org/browse/WFLY-8530
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Reporter: Jörg Bäsner
> Assignee: Scott Marlow
> Attachments: playground-prj.tar.gz
>
>
> A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly.
> The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows:
> * with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG*
> * without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8530) Wrong ZonedDateTime value read when attribute annotated with @Id
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-8530?page=com.atlassian.jira.plugin.... ]
Jörg Bäsner updated WFLY-8530:
------------------------------
Steps to Reproduce:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
~~~
10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: *2017-10-29T02:00+02:00[Europe/Berlin]*, withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: *2017-10-29T02:00+01:00[Europe/Berlin]*, offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
~~~
was:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
~~~
10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
~~~
> Wrong ZonedDateTime value read when attribute annotated with @Id
> ----------------------------------------------------------------
>
> Key: WFLY-8530
> URL: https://issues.jboss.org/browse/WFLY-8530
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Reporter: Jörg Bäsner
> Assignee: Scott Marlow
> Attachments: playground-prj.tar.gz
>
>
> A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly.
> The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows:
> * with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG*
> * without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8530) Wrong ZonedDateTime value read when attribute annotated with @Id
by Jörg Bäsner (JIRA)
[ https://issues.jboss.org/browse/WFLY-8530?page=com.atlassian.jira.plugin.... ]
Jörg Bäsner updated WFLY-8530:
------------------------------
Steps to Reproduce:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
{{10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: *2017-10-29T02:00+02:00[Europe/Berlin]*, withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: *2017-10-29T02:00+01:00[Europe/Berlin]*, offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------}}
was:
Attached is a simple maven project that can be used to reproduce this issue (a pre-build artifact is already contained in the archive).
A README.md is included guiding through the steps needed...
The output will be:
~~~
10:31:35,094 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,941 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: 2017-10-29T02:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:35,944 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:35,949 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Value --
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here all ZonedDateTimes are correct...
10:31:35,950 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,050 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 65) HHH000397: Using ASTQueryTranslatorFactory
10:31:36,719 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509235200, instant: 2017-10-29T00:00:00Z, toString: *2017-10-29T02:00+02:00[Europe/Berlin]*, withZoneSameInstant: 2017-10-29T02:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,720 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- Now read with Id on Timestamp --
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) -- here the epoch[1] is wrong...
10:31:36,721 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
10:31:36,736 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[0]: 1509231600, instant: 2017-10-28T23:00:00Z, toString: 2017-10-29T01:00+02:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T01:00+02:00[Europe/Berlin], offset: +02:00
10:31:36,737 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[1]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: *2017-10-29T02:00+01:00[Europe/Berlin]*, offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) epoch[2]: 1509238800, instant: 2017-10-29T01:00:00Z, toString: 2017-10-29T02:00+01:00[Europe/Berlin], withZoneSameInstant: 2017-10-29T02:00+01:00[Europe/Berlin], offset: +01:00
10:31:36,738 INFO [org.jboss.jbaesner.playground.jpa.TimeTestStartupBean] (ServerService Thread Pool -- 65) ------------------------------------------------------------------------------------------------
~~~
> Wrong ZonedDateTime value read when attribute annotated with @Id
> ----------------------------------------------------------------
>
> Key: WFLY-8530
> URL: https://issues.jboss.org/browse/WFLY-8530
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Reporter: Jörg Bäsner
> Assignee: Scott Marlow
> Attachments: playground-prj.tar.gz
>
>
> A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly.
> The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows:
> * with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG*
> * without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8531) [GSS] (7.0.z) Wrong ZonedDateTime value read when attribute annotated with @Id
by Jörg Bäsner (JIRA)
Jörg Bäsner created WFLY-8531:
---------------------------------
Summary: [GSS] (7.0.z) Wrong ZonedDateTime value read when attribute annotated with @Id
Key: WFLY-8531
URL: https://issues.jboss.org/browse/WFLY-8531
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 10.1.0.Final
Reporter: Jörg Bäsner
Assignee: Scott Marlow
Attachments: playground-prj.tar.gz
A ZonedDateTime entity attribute annotated with @Id returns the wrong value when read from the database. When the annotation @Id is not present, the value is returned correctly.
The special timestamp of Germanys daylight saving in October 2017 "2017-10-29T02:00:00+02:00" is returned after read as follows:
* with @Id: 2017-10-29T02:00+*01:00*[Europe/Berlin] <- *WRONG*
* without @Id: 2017-10-29T02:00+*02:00*[Europe/Berlin] <- *CORRECT*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2507) Key manager exported from legacy security domain can not be used by Elytron server-ssl-context
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2507?page=com.atlassian.jira.plugi... ]
Ondrej Kotek updated WFCORE-2507:
---------------------------------
Summary: Key manager exported from legacy security domain can not be used by Elytron server-ssl-context (was: Key manager exported from legacy security domain does not work Elytron server-ssl-context)
> Key manager exported from legacy security domain can not be used by Elytron server-ssl-context
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-2507
> URL: https://issues.jboss.org/browse/WFCORE-2507
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta6
> Reporter: Ondrej Kotek
> Priority: Critical
>
> It is not possible to use a key manager exported from legacy security domain (i.e. {{elytron-key-manager}}) in Elytron {{server-ssl-context}}. It results in:
> {noformat}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssc" => "org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssc: WFLYELY00019: No 'X509ExtendedKeyManager' found in injected value."},
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.ssl-context.ssc"]
> },
> "rolled-back" => true
> }
> {noformat}
> The exported key manager is announced as {{org.wildfly.security.key-managers}} capability. Hence it is expected to work wherever the capability is requested.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months