[jboss-jira] [JBoss JIRA] (ELY-1526) Update the default provider supplier to be an aggregate of the WildFlyElytronProvider plus the installed providers in order to ensure the WildFlyElytronProvider comes first

[Farah Juma (JIRA)]

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

Farah Juma updated ELY-1526:
----------------------------
    Description: 
As Martin Choma [mentioned|https://issues.jboss.org/browse/WFLY-9899?focusedCommentId=13537481&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13537481] on WFLY-9899, the security providers are being loaded in a different order on JDK 8 vs JDK 9. With JDK 9, the WildFlyElytronProvider is no longer at the beginning of the providers array as it is with JDK 8. With JDK 9, the providers array also contains duplicate providers - they're being added once from the service loader and once from the installed providers. 

Update the default provider supplier to be an aggregate of:

# WildFlyElytronProvider
# The security providers loaded using the service loader mechanism ensuring that any provider that is already an installed provider is skipped
# The installed providers

For WildFly 13, we can look at enhancing this by introducing a security provider selector mechanism. This is tracked in ELY-1530.

  was:As Martin Choma [mentioned|https://issues.jboss.org/browse/WFLY-9899?focusedCommentId=13537481&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13537481] on WFLY-9899, the security providers are being loaded in a different order on JDK 8 vs JDK 9. With JDK 9, the WildFlyElytronProvider is no longer at the beginning of the providers array as it is with JDK 8. With JDK 9, the providers array also contains duplicate providers - they're being added once from the service loader and once from the installed providers. As discussed with David Lloyd, the best way to fix this is likely to just have the default supplier be an aggregate of the WildFlyElytronProvider plus the installed providers and drop the service loader part.



> Update the default provider supplier to be an aggregate of the WildFlyElytronProvider plus the installed providers in order to ensure the WildFlyElytronProvider comes first
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ELY-1526
>                 URL: https://issues.jboss.org/browse/ELY-1526
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: Authentication Client
>            Reporter: Farah Juma
>            Assignee: Farah Juma
>             Fix For: 1.2.2.Final
>
>
> As Martin Choma [mentioned|https://issues.jboss.org/browse/WFLY-9899?focusedCommentId=13537481&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13537481] on WFLY-9899, the security providers are being loaded in a different order on JDK 8 vs JDK 9. With JDK 9, the WildFlyElytronProvider is no longer at the beginning of the providers array as it is with JDK 8. With JDK 9, the providers array also contains duplicate providers - they're being added once from the service loader and once from the installed providers. 
> Update the default provider supplier to be an aggregate of:
> # WildFlyElytronProvider
> # The security providers loaded using the service loader mechanism ensuring that any provider that is already an installed provider is skipped
> # The installed providers
> For WildFly 13, we can look at enhancing this by introducing a security provider selector mechanism. This is tracked in ELY-1530.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)