XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 8.0.0.GA
    • User Feedback

      I am following instructions in https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/8.0/html-single/using_single_sign-on_with_jboss_eap/index#securing-applications-deployed-on-server-with-single-sign-on_default 

      Chapter 2. Securing applications deployed on JBoss EAP with Single Sign-On

      In chapter 

      2.3.3. Securing a web application using OpenID Connect

      there is an example JBoss cli command which uses deployment name "simple-oidc-example.war":

      /subsystem=elytron-oidc-client/secure-deployment=simple-oidc-example.war/:add(client-id=jbeap-oidc,provider-url=http://localhost:8180/realms/example_realm,public-client=true,ssl-required=external)

      However, the maven project uses artifactId simple-webapp-example

      <artifactId>simple-webapp-example</artifactId>

      This caused some confusion as the resulting .war file does not match the name used in the JBoss cli command and authentication of the example web app fails without redirecting to the Keycloak login page.

              amehenda@redhat.com Ashwin Mehendale
              antero.lampi Antero Lampi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: