Our end user BOMs currently reference the Elytron shaded JAR:

<dependency>
        <groupId>org.wildfly.security</groupId>
        <artifactId>wildfly-elytron</artifactId>
</dependency>

Should Elytron itself have a couple of use case specific BOMs with transitive dependencies on Elytron modules only so application developers could depend on one artifact and get the set needed for a specific task?

To start with, it might make sense to create a BOM with everything needed so the shaded JAR doesn't need to be referenced anymore.

An EAPDOC should follow up to document this change in the EAP Migration Guide.