[JBoss JIRA] (WFCORE-4465) Ensure all transitive embedded are included by default
by James Perkins (Jira)
James Perkins created WFCORE-4465:
-------------------------------------
Summary: Ensure all transitive embedded are included by default
Key: WFCORE-4465
URL: https://issues.jboss.org/browse/WFCORE-4465
Project: WildFly Core
Issue Type: Task
Components: Embedded
Reporter: James Perkins
Assignee: James Perkins
When using the {{wildfly-embedded}} dependency it requires some additional dependencies, for example {{org.wildfly.common:wildfly-common}}, to be included. These dependencies should be examined and explicitly added as dependencies so consumers do not need to know which dependencies need to be added.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFWIP-161) OCSP configuration does not work
by Martin Mazanek (Jira)
[ https://issues.jboss.org/browse/WFWIP-161?page=com.atlassian.jira.plugin.... ]
Martin Mazanek commented on WFWIP-161:
--------------------------------------
You didn't actually set the trust-manager to use OCSP. Try this:
{code}
/subsystem=elytron/trust-manager=oscpTM:add(key-store=ocspKS, ocsp={})
{code}
> OCSP configuration does not work
> --------------------------------
>
> Key: WFWIP-161
> URL: https://issues.jboss.org/browse/WFWIP-161
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Environment: WildFly built with following branches in use:
> {code}
> https://github.com/nekdozjam/wildfly-elytron/tree/ELY-1617
> https://github.com/nekdozjam/wildfly-core/tree/WFCORE-3947
> {code}
> Reporter: Jan Stourac
> Assignee: Martin Mazanek
> Priority: Major
>
> I tried to configure OCSP support in WildFly trust-manager, although it looks like I am not able to configure it properly. After all my steps (see in 'steps to reproduce' section), my WildFly server accepts clients both with valid and revoked certificates. Although expected behavior is to accept only the one with the valid certificate.
> Looking in the OCSP responder log (OpenSSL used for this), it looks like there is even no request to it. Checked also Wireshark with same result - no request to OCSP responder on my machine.
> As such, there is probably some problem in implementation or my actual configuration is buggy. Could you please check and give some advice?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
by Ronald Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ]
Ronald Sigal commented on WFLY-11956:
-------------------------------------
[~eli.macdonald], excellent. That's great news.
> @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11956
> URL: https://issues.jboss.org/browse/WFLY-11956
> Project: WildFly
> Issue Type: Bug
> Components: Bean Validation, REST
> Affects Versions: 16.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Ronald Sigal
> Priority: Major
> Attachments: logging.txt, playground.zip
>
>
> Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_:
> {code}
> @Path("/validated")
> public interface ValidatedJaxRsInterface {
>
> @GET
> @Valid
> @Produces(MediaType.APPLICATION_JSON)
> GreetingModel getHelloGreeting();
> }
> {code}
> will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed.
> This can be reproduced with the attached reproducer application...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months