[JBoss JIRA] (WFWIP-290) Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFWIP-290?page=com.atlassian.jira.plugin... ]
Fabio Burzigotti commented on WFWIP-290:
----------------------------------------
Thanks [~pferraro]. Tests are confirming for this to be fixed with following feature branch version:
* commit: 7c53fecadc5df6b8e5f0c2795bc8b9daf58055bd
Closing the issue.
> Response Content-Type is 'application/json' even when HTTP request defines 'application/json-patch+json' "Accept" header
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-290
> URL: https://issues.redhat.com/browse/WFWIP-290
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP OpenAPI
> Reporter: Fabio Burzigotti
> Assignee: Paul Ferraro
> Priority: Major
>
> When sending HTTP request header "Accept: application/json-patch+json", "Content-Type: application/json" response is returned.
> This behavior seems to be less strict compared to what is defined by the spec, as it states "application/json" is specifically needed in order to get the same value back from server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4891) Further Optimize Lambdas in Executable Model
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-4891?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-4891:
---------------------------------
Labels: good-first-issue (was: )
> Further Optimize Lambdas in Executable Model
> --------------------------------------------
>
> Key: DROOLS-4891
> URL: https://issues.redhat.com/browse/DROOLS-4891
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
> Labels: good-first-issue
>
> Lambda shouldn't be externalized depending on the variable name but on the actual lambda.
> So
> person.name == a
> person.name == b
> Is effectively the same lambda and should externalized once.
> Hint: we could rename the parameters to p1, p2, p3, promote the types to fully qualified names and get this result.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFWIP-294) JWT is rejected if signature matching public key is not first in JWK set
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-294?page=com.atlassian.jira.plugin... ]
Jan Kasik updated WFWIP-294:
----------------------------
Description:
When public key on remote server is configured to be JWK set, the JWT which has correctly configured key ID to aim on matching public key from the set is rejected if matching public key is not on first position in the set array.
Attached is "flawed" key set with "blue-key" placed on first position in array when JOSE header has {{kid}} set to "orange-key" and JWT itself is signed by private key which is from "orange" key pair.
was:
When public key on remote server is configured to be JWK set, the JWT which has correctly configured key ID to aim on matching public key from the set is rejected if matching public key is not on first position in the set array.
Attached is "flawed" key set with "blue-key" placed on first position in array.
> JWT is rejected if signature matching public key is not first in JWK set
> ------------------------------------------------------------------------
>
> Key: WFWIP-294
> URL: https://issues.redhat.com/browse/WFWIP-294
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP JWT
> Reporter: Jan Kasik
> Assignee: Darran Lofthouse
> Priority: Blocker
> Attachments: jwks.json, jwt.base64
>
>
> When public key on remote server is configured to be JWK set, the JWT which has correctly configured key ID to aim on matching public key from the set is rejected if matching public key is not on first position in the set array.
> Attached is "flawed" key set with "blue-key" placed on first position in array when JOSE header has {{kid}} set to "orange-key" and JWT itself is signed by private key which is from "orange" key pair.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months