[JBoss JIRA] (WFLY-13638) Permit multiples applications to the same server registry a MP openapi endpoint
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13638?page=com.atlassian.jira.plugi... ]
Paul Ferraro commented on WFLY-13638:
-------------------------------------
[~rhn-support-rhsilva] While I agree with you, i.e. exposing the /openapi endpoint at the context root instead of the host root makes a lot of sense for a traditional application server (as opposed to a single deployment MicroProfile container (e.g. Quarkus, ThornTail, etc.), this would unfortunately violate the MicroProfile OpenAPI specification.
Instead, the specification indicates that the OpenAPI endpoint should return documentation of all REST endpoints available from the host (including all contexts deployed to that host). We don't yet have the ability to merge the OpenAPI model for each application, but that is currently the plan.
> Permit multiples applications to the same server registry a MP openapi endpoint
> -------------------------------------------------------------------------------
>
> Key: WFLY-13638
> URL: https://issues.redhat.com/browse/WFLY-13638
> Project: WildFly
> Issue Type: Feature Request
> Components: MP OpenAPI
> Affects Versions: 20.0.0.Final
> Reporter: Rhuan Rocha
> Assignee: Paul Ferraro
> Priority: Major
>
> In the Wildfly 20, if I deploy two applications in the same server just one registry an openapi endpoint. Look at this code:
> [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d492c2...]
>
> It makes sense as the endpoint is registered to http://{host}:\{port}/openpi, but I think it is better to registry it considering the context root. With this, we can registry multiples openapi per server. Thus the openapi endpoint can be registered to http://{host}:\{port}/\{context-root}/openapi. Looking at the code looks like it is possible to be done. If we have access to the information of context-root in [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d4..., then we can start it considering the context-root. I think it will be a very common scenario of use and it will be very helpful to users.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5473) Implement DefineFunction scheleton
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5473?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5473:
-------------------------------------
Labels: TrustyAI (was: )
> Implement DefineFunction scheleton
> ----------------------------------
>
> Key: DROOLS-5473
> URL: https://issues.redhat.com/browse/DROOLS-5473
> Project: Drools
> Issue Type: Sub-task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Implement DefineFunction management scheleton.
> DefineFunctions are similar to DerivedFields, since both make usage of EXPRESSION.
> Differences are
> 1) DerivedFields methods should referenced inside "transformations" map, DefineFunctions not
> 2) DerivedFields methods names are automatically generated, while DefineFunctions ones are retrieved from DefinedFunctions declaration
> 3) DefineFunctions requires at least one Parameter (beside the List of already defined fields )
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ELY-2004) SPNEGO mechanism handles delegated credential twice.
by Darran Lofthouse (Jira)
Darran Lofthouse created ELY-2004:
-------------------------------------
Summary: SPNEGO mechanism handles delegated credential twice.
Key: ELY-2004
URL: https://issues.redhat.com/browse/ELY-2004
Project: WildFly Elytron
Issue Type: Bug
Components: HTTP
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.13.0.CR2
>From a successful authentication with a delegated credential we can see from the logs the delegated credential is handled twice.
{code:java}
2020-07-01 20:19:30,820 TRACE [org.wildfly.security.http.spnego] (default task-1) Associating delegated GSSCredential with identity.
2020-07-01 20:19:30,822 TRACE [org.wildfly.security.http.spnego] (default task-1) GSSContext established, authorizing...
2020-07-01 20:19:30,822 TRACE [org.wildfly.security.http.spnego] (default task-1) Credential delegation enabled, delegated credential = [GSSCredential:
admin(a)ELYTRON.ORG 1.2.840.113554.1.2.2 Initiate [class sun.security.jgss.krb5.Krb5InitCredential]
admin(a)ELYTRON.ORG 1.3.6.1.5.5.2 Initiate [class sun.security.jgss.spnego.SpNegoCredElement]] {code}
The first can be removed as we will always move onto the second if the GSSContext is establihsed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years