anchor.diff:    <realm-name>Test Realm</realm-name>
   </login-config>
   ....
  -
  -==== JASPI Authentication
  -
  -A Java Authentication SPI (JASPI) provider can be configured in WildFly
  -security subsystem to authenticate SOAP messages:
  -
  -....
  -<security-domain name="jaspi">
  -      <authentication-jaspi>
  -          <login-module-stack name="jaas-lm-stack">
  -             <login-module code="UsersRoles" flag="required">
  -                  <module-option name="usersProperties" value="jbossws-users.properties"/>
  -                  <module-option name="rolesProperties" value="jbossws-roles.properties"/>
  -             </login-module>
  -          </login-module-stack>
  -          <auth-module code="org.jboss.wsf.stack.cxf.jaspi.module.UsernameTokenServerAuthModule" login-module-stack-ref="jaas-lm-stack"/>
  -     </authentication-jaspi>
  - </security-domain>
  -....
  -
  -[IMPORTANT]
  -====
  -For further information on configuring security in WildFly,
  -please refer to
  -https://docs.wildfly.org/26/#security-guide[here]
  -.
  -====
  -
  -Here
  -`org.jboss.wsf.stack.cxf.jaspi.module.UsernameTokenServerAuthModule` is
  -the class implementing
  -`javax.security.auth.message.module.ServerAuthModule` , which delegates
  -to the proper login module to perform authentication using the
  -credentials from WS-Security UsernameToken in the incoming SOAP message.
  -Alternative implementations of `ServerAuthModule` can be implemented and
  -configured.
  -
  -To enable JASPI authentication, the endpoint deployment needs to specify
  -the security domain to use; that can be done in two different ways:
  -
  -* Setting the `jaspi.security.domain` property in the
  -`jboss-webservices.xml` descriptor
  -
  -....
  -<?xml version="1.1" encoding="UTF-8"?>
  -<webservices
  -  xmlns="http://www.jboss.com/xml/ns/javaee"
  -  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  -  version="1.2"
  -  xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee">
  -
  -  <property>
  -    <name>jaspi.security.domain</name>
  -    <value>jaspi</value>
  -  </property>
  -
  -</webservices>
  -....
  -
  -* Referencing (through `@EndpointConfig` annotation) an endpoint config
  -that sets the `jaspi.security.domain` property
  -
  -....
  -@EndpointConfig(configFile = "WEB-INF/jaxws-endpoint-config.xml", configName = "jaspiSecurityDomain")
  -public class ServiceEndpointImpl implements ServiceIface {
  -....
  -
  -The `jaspi.security.domain` property is specified as follows in the
  -referenced descriptor:
  -
  -....
  -<?xml version="1.0" encoding="UTF-8"?>
  -<jaxws-config xmlns="urn:jboss:jbossws-jaxws-config:4.0"
  -    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  -    xsi:schemaLocation="urn:jboss:jbossws-jaxws-config:4.0 schema/jbossws-jaxws-config_4_0.xsd">
  -    <endpoint-config>
  -        <config-name>jaspiSecurityDomain</config-name>
  -        <property>
  -            <property-name>jaspi.security.domain</property-name>
  -            <property-value>jaspi</property-value>
  -        </property>
  -    </endpoint-config>
  -</jaxws-config>
  -....
  -
  -[NOTE]
  -====
  -If the JASPI security domain is specified in both
  -`jboss-webservices.xml` and config file referenced by `@EndpointConfig`
  -annotation, the JASPI security domain specified in
  -`jboss-webservices.xml` will take precedence.
  -====
  -
   
   === Apache CXF integration
   
  
positive.code: import org.apache.cxf.annotations.EndpointProperties;
  import org.apache.cxf.annotations.EndpointProperty;
  
  import javax.jws.WebService;
  
  @WebService
  (
  
negative.code: ....
  
  ....
  import jakarta.jws.WebService;
  import org.jboss.ws.api.annotation.EndpointConfig;
  
  @WebService
  