Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16840

Doc: Server-to-server remote EJB with Elytron config

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Documentation, Security
    • None

    Description

      The current WildFly & EAP 7 docs don't cover the server-to-server remote EJB invocation scenario with the Elytron security subsystem in place of the legacy security subsystem.

      At the 2 URLs below there's only the legacy security variant described for this case with no traces of the Elytron variant at all:

      https://docs.wildfly.org/26.1/Developer_Guide.html#packaging-the-client-application-on-the-client-server

      https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html/developing_jakarta_enterprise_beans_applications/clustered_jakarta_enterprise_beans#remote_clients_on_another_instance

      There's no such information in the migration guides either:

      https://docs.wildfly.org/26.1/Migration_Guide.html

      https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.4/html/migration_guide/migrating_to_elytron

      And it isn't even in the WildFly Elytron security guide:

      https://docs.wildfly.org/26.1/WildFly_Elytron_Security.html

      Meaning that it isn't fully documented anywhere at all.

      The only place where I found something like this is the following 5 years old blog post:
      https://developer.jboss.org/people/fjuma/blog/2017/09/08/getting-started-with-ejbs-and-elytron-part-2
      which may be outdated to some extent and/or lack some further details.

      Since Elytron is the preferred security subsystem going forward, could you please update the docs (both WildFly & EAP) to cover the server-to-server remove EJB invocation scenario?

      Attachments

        Activity

          People

            Unassigned Unassigned
            petr.hostalek@bsc-ideas.com Petr Hostalek (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: