[jboss-jira] [JBoss JIRA] (WFLY-8325) Connector module 'authentication-context' attributes should not support expressions and should be capability references if the target resource provides a capability

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved JBEAP-9432 to WFLY-8325:
-----------------------------------------------

        Project: WildFly  (was: JBoss Enterprise Application Platform)
            Key: WFLY-8325  (was: JBEAP-9432)
       Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
    Component/s: JCA
                     (was: JCA)


> Connector module 'authentication-context' attributes should not support expressions and should be capability references if the target resource provides a capability
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8325
>                 URL: https://issues.jboss.org/browse/WFLY-8325
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Blocker
>
> The various "authentication-context" attributes added into the connector module for the elytron integration say they support expressions. They shouldn't, as model references should not support expressions as these interfere with model referential integrity checks.
> Also, where possible the attribute definitions should be configured as capability references, thus automatically turning on the kernel's referential integrity checks and allowing CLI and HAL value completion.
> The latter is only possible for ADs where the containing resource exposes a capability itself. The DS and XA DS resources do. I'm not sure about RAs but I suspect they don't yet.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)