hal / berg Goto Github PK
View Code? Open in Web Editor NEWHAL test suite based on Cypress
Home Page: https://hal.github.io/berg/
License: Apache License 2.0
HAL test suite based on Cypress
Home Page: https://hal.github.io/berg/
License: Apache License 2.0
The side menu of generated documentation doesn't navigate directly to method description.
Find or create new theme which will create better navigation menu.
None
None
The basic tests migrated from legacy TS doesn't seem to be complex enough, see #34 and #96.
We should also be testing:
configuration
transaction
Provide more information about environment variables required by podman.
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Other Settings => Stores.
There are five vertical navigation sub-items, hence five new spec files are expected: Credential Store
, Filtering Key Store
, Key Store
, LDAP Key Store
, Secret Key Credential Store
.
Resources to be covered
/subsystem=elytron/credential-store=*
/subsystem=elytron/filtering-key-store=*
/subsystem=elytron/key-store=*
/subsystem=elytron/ldap-key-store=*
/subsystem=elytron/secret-key-credential-store=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Other Settings => Logs.
There are six vertical navigation sub-items, hence six new spec files are expected: Aggregate Security Event Listener
, Custom Security Event Listener
, File Audit Log
, Periodic Rotating File Audit Log
, Size Rotating File Audit Log
, Syslog Audit Log
.
Resources to be covered
/subsystem=elytron/aggregate-security-event-listener=*
/subsystem=elytron/custom-security-event-listener=*
/subsystem=elytron/file-audit-log=*
/subsystem=elytron/periodic-rotating-file-audit-log=*
/subsystem=elytron/size-rotating-file-audit-log=*
/subsystem=elytron/syslog-audit-log=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Handlers) is missing.
There are two vertical navigation items, hence two spec files are expected: File Handler
, Reverse Proxy
.
Resources to be covered
/subsystem=undertow/configuration=handler/file=*
/subsystem=undertow/configuration=handler/reverse-proxy=*
/subsystem=undertow/configuration=handler/reverse-proxy=*/host=*
You can get inspired in legacy tests.
configuration
undertow
Migrate Deployments tests from hal/testsuite.next to this test suite.
deployment
None
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Mappers/Decoders => Permission Mapper.
There are four vertical navigation sub-items, hence four new spec files are expected: Custom Permission Mapper
, Logical Permission Mapper
, Constant Permission Mapper
, Simple Permission Mapper
.
Resources to be covered
/subsystem=elytron/custom-permission-mapper=*
/subsystem=elytron/logical-permission-mapper=*
/subsystem=elytron/constant-permission-mapper=*
/subsystem=elytron/simple-permission-mapper=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Buffer Caches) is missing.
Resources to be covered
/subsystem=undertow/buffer-cache=*
You can get inspired in legacy tests.
configuration
undertow
Currently, we're missing coverage of the discovery subsystem configuration (Configuration => Subsystem => Elytron OIDC Client).
Elytron OIDC Client subsystem page is a generic subsystem page and contains "provider", "realm" and "secure-deployment" vertical navigation items, expecting three spec files to be created
Resources to cover (from /subsystem=elytron-oidc-client:read-resource(recursive=true)
):
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*
/subsystem=elytron-oidc-client/secure-deployment=*/adapter-state-cookie-path
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/allow-any-hostname
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/always-refresh-token
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/auth-server-url
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/autodetect-bearer-only
/subsystem=elytron-oidc-client/secure-deployment=*/bearer-only
/subsystem=elytron-oidc-client/secure-deployment=*/client-id
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/client-key-password
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/client-keystore
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/client-keystore-password
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/confidential-port
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/connection-pool-size
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/connection-timeout-millis
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/connection-ttl-millis
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/cors-allowed-headers
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/cors-allowed-methods
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/cors-exposed-headers
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/cors-max-age
/subsystem=elytron-oidc-client/secure-deployment=*/credential
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/disable-trust-manager
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/enable-cors
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/expose-token
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/ignore-oath-query-parameter
/subsystem=elytron-oidc-client/secure-deployment=*/min-time-between-jwks-requests
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/principal-attribute
/subsystem=elytron-oidc-client/secure-deployment=*/provider
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]r=*/provider-url
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/proxy-url
/subsystem=elytron-oidc-client/secure-deployment=*/public-client
/subsystem=elytron-oidc-client/secure-deployment=*/public-key-cache-ttl
/subsystem=elytron-oidc-client/secure-deployment=*/realm
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/realm-public-key
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/register-node-at-startup
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/register-node-period
/subsystem=elytron-oidc-client/secure-deployment=*/resource
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/socket-timeout-millis
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]r=*/ssl-required
/subsystem=elytron-oidc-client/secure-deployment=*/token-minimum-time-to-live
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/token-signature-algorithm
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/token-store
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/truststore
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/truststore-password
/subsystem=elytron-oidc-client/secure-deployment=*/turn-off-change-session-id-on-login
/subsystem=elytron-oidc-client/secure-deployment=*/use-resource-role-mappings
/subsystem=elytron-oidc-client/[provider|realm|secure-deployment]=*/verify-token-audience/
configuration
elytron-oidc-client
Migrate CustomConsoleTitleTest from hal/testsuite.next to this test suite.
Migrate Runtime tests from hal/testsuite.next to this test suite.
Note that there are already some tests for open ports and server status, and some tests configuring server through this navigation may be covered by some other issues.
runtime
None
Coverage of the server (management) configuration (Runtime => Server => View) is missing.
There are three vertical navigation items, hence three spec files are expected: Configuration
, HTTP Management Interface
, Constant Headers
.
Resources to be covered
/core-service=management/management-interface=http-interface
/
You can get inspired in legacy tests.
runtime
None
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Security Realms => Realm Mappers.
There are four vertical navigation sub-items, hence four new spec files are expected: Constant Realm Mapper
, Custom Realm Mapper
, Mapped Regex Realm Mapper
, Simple Regex Realm Mapper
.
Resources to be covered
/subsystem=elytron/constant-realm-mapper=*
/subsystem=elytron/custom-realm-mapper=*
/subsystem=elytron/mapped-regex-realm-mapper=*
/subsystem=elytron/simple-regex-realm-mapper=*
You can get inspired in legacy tests.
configuration
elytron
Currently, we are running CI jobs in parallel, dividing the spec (test) files by regular expressions. Currently we have coverage for following subsystems:
datasource
interface
path
batch-jberet
core-management
deployment-scanner
distributable-web
ee
ejb
elytron
jmx
jpa
jsf
system-property
weld
The aim of this test suite is to provide full UI coverage of the management console. As such, we need to have coverage of all subsystems that can be interacted with via UI. Following is the list of all subsystems that we want to cover:
batch
datasource
deployment-scanner
discovery
distributable-web
ee
ejb
elytron
elytron-oidc-client
health
iiop
io
infinispan
interface
jaxrs
jca
jgroups
jmx
jpa
jsf
logging
mail
messaging
metrics
microprofile-config
microprofile-jwt-smallrye
modcluster
naming
remoting
request-controller
resource-adapters
singleton
system-property
transaction
undertow
web-services
weld
Some of the subsystem names may collide (e.g elytron
and elytron-oidc-client
) and some of the tests may incorporate some of the listed tokens. This could be separated by a mighty regex, but creating subsystem subdirectories would be more clean & clear way of doing this.
Currently, we're missing coverage of the discovery subsystem configuration (Configuration => Subsystem => Discovery).
Discovery subsystem page is a generic subsystem page and contains "aggregated-provider" and "static-provider" vertical navigation items, expecting one or two spec files to be created
Resources to cover (from /subsystem=discovery:read-resource(recursive=true)
):
/subsystem=discovery/static-provider=*/
/subsystem=discovery/aggregate-provider=*/
configuration
discovery
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Security Realms => Security Realm.
There are eleven vertical navigation sub-items, hence eleven new spec files are expected: Aggregate Realm
, Caching Realm
, Custom Modifiable Realm
, Custom Realm
, Filesystem Realm
, Identity Realm
, JDBC Realm
, Key Store Realm
, LDAP Realm
, Properties Realm
, Token Realm
.
Resources to be covered
/subsystem=elytron/aggregate-realm=*
/subsystem=elytron/caching-realm=*
/subsystem=elytron/custom-modifiable-realm=*
/subsystem=elytron/custom-realm=*
/subsystem=elytron/filesystem-realm=*
/subsystem=elytron/identity-realm=*
/subsystem=elytron/jdbc-realm=*
/subsystem=elytron/key-store-realm=*
/subsystem=elytron/ldap-realm=*
/subsystem=elytron/properties-realm=*
/subsystem=elytron/token-realm=*
You can get inspired in legacy tests.
configuration
elytron
Migrate Configuration tests from hal/testsuite.next to this test suite.
configuration
None
See https://issues.redhat.com/browse/JBEAP-25005 for details.
Can we workaround this by clicking Close, or reloading, or using a short sleep?
Migrate NonProgressingNotificationTest and NotificationTest from hal/testsuite.next to this test suite.
Currently, we're missing coverage of the IO subsystem configuration (Configuration => Subsystem => IO).
IO subsystem page contains "worker" and "buffer-pool" vertical navigation items, expecting two spec files to be created
Resources to cover (from /subsystem=io:read-resource(recursive=true)
):
/subsystem/io/buffer-pool
/subsystem/io/buffer-pool=*/buffer-size
/subsystem/io/buffer-pool=*/buffers-per-slice
/subsystem/io/buffer-pool=*/direct-buffers
/subsystem/io/worker=*/io-threads
/subsystem/io/worker=*/stack-size
/subsystem/io/worker=*/task-core-threads
/subsystem/io/worker=*/task-keepalive
/subsystem/io/worker=*/task-max-threads
/subsystem/io/worker=*/outbound-bind-address
/subsystem/io/worker=*/server
configuration
io
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Other Settings => Other Settings.
There are seven vertical navigation sub-items, hence seven new spec files are expected: Certificate Authority
, Certificate Authority Account
, Dir Context
, Expression
, JASPI Configuration
, Permission Set
, JACC Policy
.
Resources to be covered
/subsystem=elytron/certificate-authority=*
/subsystem=elytron/certificate-authority-account=*
/subsystem=elytron/dir-context=*
/subsystem=elytron/expression=encryption
/subsystem=elytron/jaspi-configuration=*
/subsystem=elytron/permission-set=*
/subsystem=elytron/policy=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Other Settings => Authentication.
There are two vertical navigation sub-items, hence two new spec files are expected: Authentication Configuration
, Authentication Context
.
Resources to be covered
/subsystem=elytron/authentication-configuration=*
/subsystem=elytron/authentication-context=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Mappers/Decoders => Evidence Decoder.
There are four vertical navigation sub-items, hence four new spec files are expected: Aggregate Evidence Decoder
, Custom Evidence Decoder
, X500 Subject Evidence Decoder
, X509 Subject Alt Name Evidence Decoder
.
Resources to be covered
/subsystem=elytron/aggregate-evidence-decoder=*
/subsystem=elytron/custom-evidence-decoder=*
/subsystem=elytron/x500-subject-evidence-decoder=*
/subsystem=elytron/x509-subject-alt-name-evidence-decoder=*
You can get inspired in legacy tests.
configuration
elytron
Currently, we're missing coverage of the discovery subsystem configuration (Configuration => Subsystem => Health).
Health subsystem page is a generic subsystem page and contains only "health" vertical navigation item
health
module.Expected resources to cover from /subsystem=health:read-resource(recursive=true):
/subsystem=health/security-enabled
configuration
health
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Byte Buffer Pool) is missing.
Resources to be covered
/subsystem=undertow/byte-buffer-pool=*
You can get inspired in legacy tests.
configuration
undertow
#32 and #35 removes failing Reset tests. The removed tests should be replaced by a check that the None of the attributes could be reset. warning is displayed.
For inspiration: https://github.com/hal/berg/blob/main/packages/testsuite/cypress/support/verification-utils.ts#L3
configuration
distributable-web
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Global Settings) is missing.
One spec file is expected.
Resources to be covered
/subsystem=undertow
You can get inspired in legacy tests.
configuration
undertow
Currently, we're missing coverage of the Mail subsystem configuration (Configuration => Subsystem => Mail).
Mail subsystem page contains "attributes" and "server" vertical navigation items + user is able to create "mail-session" from the finder fragments, expecting three spec files to be created
Resources to cover (from /subsystem=mail:read-resource(recursive=true)
):
/subsystem/mail/mail-session
/subsystem/mail/mail-session=*/debug
/subsystem/mail/mail-session=*/from
/subsystem/mail/mail-session=*/jndi-name
/subsystem/mail/mail-session=*/custom
/subsystem/mail/mail-session=*/server
/subsystem/mail/mail-session=*/server=*/credential-reference
/subsystem/mail/mail-session=*/server=*/outbound-socket-binding-ref
/subsystem/mail/mail-session=*/server=*/password
/subsystem/mail/mail-session=*/server=*/ssl
/subsystem/mail/mail-session=*/server=*/tls
/subsystem/mail/mail-session=*/server=*/username
configuration
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Server) is missing.
There are three vertical navigation items, hence three spec files are expected: Configuration
, Hosts
, Listener
.
Resources to be covered
/subsystem=undertow/server=*
/subsystem=undertow/server=*/ajp-listener=*
/subsystem=undertow/server=*/host=*/filter-ref=*
/subsystem=undertow/server=*/host=*/location=*
/subsystem=undertow/server=*/host=*/location=*/filter-ref=*
/subsystem=undertow/server=*/host=*/setting=access-log
/subsystem=undertow/server=*/host=*/setting=console-access-log
/subsystem=undertow/server=*/host=*/setting=http-invoker
/subsystem=undertow/server=*/host=*/setting=single-sign-on
/subsystem=undertow/server=*/http-listener=*
/subsystem=undertow/server=*/https-listener=*
You can get inspired in legacy tests.
configuration
undertow
Coverage of the transaction subsystem configuration (Configuration => Subsystem => Transaction) is missing.
There are five vertical navigation items, hence five spec files are expected: Configuration
, Process
, Recovery
, Path
, JDBC
.
Resources to be covered
/subsystem=transactions
/subsystem=transactions/commit-markable-resource
/subsystem=transactions/log-store
You can get inspired in legacy tests.
configuration
transaction
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Servlet Container) is missing.
There are six vertical navigation items, hence six spec files are expected: Configuration
, JSP
, Web Sockets
, Sessions
, Cookies
, Crawler
.
Resources to be covered
/subsystem=undertow/servlet-container=*
/subsystem=undertow/servlet-container=*/mime-mapping=*
/subsystem=undertow/servlet-container=*/setting=affinity-cookie
/subsystem=undertow/servlet-container=*/setting=crawler-session-management
/subsystem=undertow/servlet-container=*/setting=jsp
/subsystem=undertow/servlet-container=*/setting=persistent-sessions
/subsystem=undertow/servlet-container=*/setting=session-cookie
/subsystem=undertow/servlet-container=*/setting=websockets
/subsystem=undertow/servlet-container=*/welcome-file=*
You can get inspired in legacy tests.
configuration
undertow
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Factories/Transformers => Other Factories.
There are two vertical navigation sub-items, hence two new spec files are expected: Kerberos Security Factory
, Custom Credential Security Factory
.
Resources to be covered
/subsystem=elytron/kerberos-security-factory=*
/subsystem=elytron/custom-credential-security-factory=*
You can get inspired in legacy tests.
configuration
elytron
Migrate multihosts tests from hal/testsuite.next to this test suite.
runtime
None
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Filters) is missing.
There are eight vertical navigation items, hence eight spec files are expected: Custom Filter
, Error Page
, Expression Filter
, GZip
, Mod Cluster Filter
, Request Limit
, Response Header
, Rewrite
.
Resources to be covered
/subsystem=undertow/configuration=filter/custom-filter=*
/subsystem=undertow/configuration=filter/error-page=*
/subsystem=undertow/configuration=filter/expression-filter=*
/subsystem=undertow/configuration=filter/gzip=*
/subsystem=undertow/configuration=filter/mod-cluster=*
/subsystem=undertow/configuration=filter/mod-cluster=*/affinity=*
/subsystem=undertow/configuration=filter/mod-cluster=a/balancer=*
/subsystem=undertow/configuration=filter/mod-cluster=a/balancer=*/load-balancing-group=*
/subsystem=undertow/configuration=filter/mod-cluster=a/balancer=*/node=*
/subsystem=undertow/configuration=filter/mod-cluster=a/balancer=*/node=*/context=*
/subsystem=undertow/configuration=filter/request-limit=*
/subsystem=undertow/configuration=filter/response-header=*
/subsystem=undertow/configuration=filter/rewrite=*
You can get inspired in legacy tests.
configuration
undertow
Migrate vulnerability tests from hal/testsuite.next to this test suite.
Coverage of the infinispan subsystem configuration (Configuration => Subsystem => Infinispan) is missing.
There are three or four vertical navigation items for cache resources, hence three or four spec files are expected per cache type: Configuration
, Memory
, Store
, Backup
.
Resources to be covered
/subsystem=infinispan/cache-container
/subsystem=infinispan/cache-container=xxx/cache
/subsystem=infinispan/cache-container=xxx/cache=yyy/component
/subsystem=infinispan/cache-container=xxx/distributed-cache
/subsystem=infinispan/cache-container=xxx/distributed-cache=yyy/component
/subsystem=infinispan/cache-container=xxx/distributed-cache=yyy/memory
/subsystem=infinispan/cache-container=xxx/distributed-cache=yyy/store
/subsystem=infinispan/cache-container=xxx/invalidation-cache
/subsystem=infinispan/cache-container=xxx/invalidation-cache=yyy/component
/subsystem=infinispan/cache-container=xxx/invalidation-cache=yyy/memory
/subsystem=infinispan/cache-container=xxx/invalidation-cache=yyy/store
/subsystem=infinispan/cache-container=xxx/local-cache
/subsystem=infinispan/cache-container=xxx/local-cache=yyy/component
/subsystem=infinispan/cache-container=xxx/local-cache=yyy/memory
/subsystem=infinispan/cache-container=xxx/local-cache=yyy/store
/subsystem=infinispan/cache-container=xxx/replicated-cache
/subsystem=infinispan/cache-container=xxx/replicated-cache=yyy/component
/subsystem=infinispan/cache-container=xxx/replicated-cache=yyy/memory
/subsystem=infinispan/cache-container=xxx/replicated-cache=yyy/store
/subsystem=infinispan/cache-container=xxx/scattered-cache
/subsystem=infinispan/cache-container=xxx/scattered-cache=yyy/component
/subsystem=infinispan/cache-container=xxx/scattered-cache=yyy/memory
/subsystem=infinispan/cache-container=xxx/scattered-cache=yyy/store
/subsystem=infinispan/cache-container=xxx/thread-pool
/subsystem=infinispan/cache-container=xxx/transport
/subsystem=infinispan/remote-cache-container
/subsystem=infinispan/remote-cache-container=xxx/component
/subsystem=infinispan/remote-cache-container=xxx/remote-cache
/subsystem=infinispan/remote-cache-container=xxx/remote-cluster
/subsystem=infinispan/remote-cache-container=xxx/thread-pool
You can get inspired in legacy tests.
configuration
infinispan
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Other Settings => SSL.
There are eight vertical navigation sub-items, hence eight new spec files are expected: Aggregate Providers
, Client SSL Context
, Key Manager
, Provider Loader
, Security Domain
, Server SSL Context
, Server SSL SNI Context
, Trust Manager
.
Resources to be covered
/subsystem=elytron/aggregate-providers=*
/subsystem=elytron/client-ssl-context=*
/subsystem=elytron/client-ssl-context=*/ssl-session=*
/subsystem=elytron/key-manager=*
/subsystem=elytron/provider-loader=*
/subsystem=elytron/security-domain=*
/subsystem=elytron/server-ssl-context=*
/subsystem=elytron/server-ssl-context=*/ssl-session=*
/subsystem=elytron/server-ssl-sni-context=*
/subsystem=elytron/trust-manager=*
You can get inspired in legacy tests.
configuration
elytron
Currently, we're missing coverage of the securitymanager subsystem configuration (Configuration => Subsystem => Security Manager).
Security Manager subsystem page contains "minimum permissions" and "maximum permissions" vertical navigation items, expecting two spec files to be created
Resources to cover (from /subsystem=securitymanager:read-resource(recursive=true)
):
/subsystem=security-manager/deployment-permissions=default/minimum-permissions
/subsystem=security-manager/deployment-permissions=default/minimum-permissions/actions
/subsystem=security-manager/deployment-permissions=default/minimum-permissions/class
/subsystem=security-manager/deployment-permissions=default/minimum-permissions/module
/subsystem=security-manager/deployment-permissions=default/minimum-permissions/name
/subsystem=security-manager/deployment-permissions=default/maximum-permissions
/subsystem=security-manager/deployment-permissions=default/maximum-permissions/actions
/subsystem=security-manager/deployment-permissions=default/maximum-permissions/class
/subsystem=security-manager/deployment-permissions=default/maximum-permissions/module
/subsystem=security-manager/deployment-permissions=default/maximum-permissions/name
You can get inspired by the tests in the legacy testsuite
configuration
securitymanager
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Mappers/Decoders => Role Mapper.
There are seven vertical navigation sub-items, hence seven new spec files are expected: Add Prefix Role Mapper
, Add Suffix Role Mapper
, Aggregate Role Mapper
, Constant Role Mapper
, Custom Role Mapper
, Logical Role Mapper
, Mapped Role Mapper
.
Resources to be covered
/subsystem=elytron/add-prefix-role-mapper=*
/subsystem=elytron/add-suffix-role-mapper=*
/subsystem=elytron/aggregate-role-mapper=*
/subsystem=elytron/constant-role-mapper=*
/subsystem=elytron/custom-role-mapper=*
/subsystem=elytron/logical-role-mapper=*
/subsystem=elytron/mapped-role-mapper=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Mappers/Decoders => Principal Decoder.
There are five vertical navigation sub-items, hence five new spec files are expected: Aggregate Principal Decoder
, Concatenating Principal Decoder
, Constant Principal Decoder
, Custom Principal Decoder
, X500 Attribute Principal Decoder
.
Resources to be covered
/subsystem=elytron/aggregate-principal-decoder=*
/subsystem=elytron/concatenating-principal-decoder=*
/subsystem=elytron/constant-principal-decoder=*
/subsystem=elytron/custom-principal-decoder=*
/subsystem=elytron/x500-attribute-principal-decoder=*
You can get inspired in legacy tests.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Factories/Transformers => HTTP Factories.
There are five vertical navigation sub-items, where Provider HTTP Server Mechanism Factory
and Service Loader HTTP Server Mechanism Factory
are alredy covered, hence three new spec files are expected: Aggregate HTTP Server Mechanism Factory
, Configurable HTTP Server Mechanism Factory
, HTTP Authentication Factory
.
Resources to be covered
/subsystem=elytron/provider-http-server-mechanism-factory=*
/subsystem=elytron/service-loader-http-server-mechanism-factory=*
/subsystem=elytron/http-authentication-factory=*
You can get inspired in legacy tests.
configuration
elytron
Migrate TakeTourTest from hal/testsuite.next to this test suite.
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Mappers/Decoders => Role Decoder.
There are two vertical navigation sub-items, hence two new spec files are expected: Custom Role Decoder
, Simple Role Decoder
.
Resources to be covered
/subsystem=elytron/custom-role-decoder=*
/subsystem=elytron/simple-role-decoder=*
You can get inspired in legacy tests.
configuration
elytron
Currently, we're missing coverage of the discovery subsystem configuration (Configuration
=> Subsystems
=> Metrics
).
Metrics subsystem page is a generic subsystem page and contains only "metrics" vertical navigation item
metrics
module.Expected resources to cover from /subsystem=health:read-resource(recursive=true)
:
/subsystem=metrics/exposed-subsystems
/subsystem=metrics/prefix
/subsystem=metrics/security-enabled
configuration
metrics
None
None
Coverage of the undertow subsystem configuration (Configuration => Subsystem => Web (Undertow) => Application Security Domain) is missing.
Resources to be covered
/subsystem=undertow/application-security-domain=*
/subsystem=undertow/application-security-domain=*/setting=single-sign-on
You can get inspired in legacy tests.
configuration
undertow
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Factories/Transformers => SASL Factories.
There are six vertical navigation sub-items, hence six new spec files are expected: Aggregate SASL Server Factory
, Configurable SASL Server Factory
, Mechanism Provider Filtering SASL Server Factory
, Provider SASL Server Factory
, SASL Authentication Factory
, Service Loader SASL Server Factory
.
Resources to be covered
/subsystem=elytron/aggregate-sasl-server-factory=*
/subsystem=elytron/configurable-sasl-server-factory=*
/subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=*
/subsystem=elytron/provider-sasl-server-factory=*
/subsystem=elytron/sasl-authentication-factory=*
/subsystem=elytron/service-loader-sasl-server-factory=*
You can get inspired in legacy tests.
configuration
elytron
Migrate Let's Encrypt tests from hal/testsuite.next to this test suite.
configuration
elytron
Coverage of the elytron subsystem configuration is missing for Configuration => Subsystem => Security => Factories/Transformers => Principal Transformers.
There are six vertical navigation sub-items, hence six new spec files are expected: Aggregate Principal Transformer
, Chained Principal Transformer
, Constant Principal Transformer
, Custom Principal Transformer
, Regex Principal Transformer
, Regex Validating Principal Transformer
.
Resources to be covered
/subsystem=elytron/aggregate-principal-transformer=*
/subsystem=elytron/chained-principal-transformer=*
/subsystem=elytron/constant-principal-transformer=*
/subsystem=elytron/custom-principal-transformer=*
/subsystem=elytron/regex-principal-transformer=*
/subsystem=elytron/regex-validating-principal-transformer=*
You can get inspired in legacy tests.
configuration
elytron
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.