Skip to main content
Redhat Developers  Logo
  • Products

    Platforms

    • Red Hat Enterprise Linux
      Red Hat Enterprise Linux Icon
    • Red Hat AI
      Red Hat AI
    • Red Hat OpenShift
      Openshift icon
    • Red Hat Ansible Automation Platform
      Ansible icon
    • View All Red Hat Products

    Featured

    • Red Hat build of OpenJDK
    • Red Hat Developer Hub
    • Red Hat JBoss Enterprise Application Platform
    • Red Hat OpenShift Dev Spaces
    • Red Hat OpenShift Local
    • Red Hat Developer Sandbox

      Try Red Hat products and technologies without setup or configuration fees for 30 days with this shared Openshift and Kubernetes cluster.
    • Try at no cost
  • Technologies

    Featured

    • AI/ML
      AI/ML Icon
    • Linux
      Linux Icon
    • Kubernetes
      Cloud icon
    • Automation
      Automation Icon showing arrows moving in a circle around a gear
    • View All Technologies
    • Programming Languages & Frameworks

      • Java
      • Python
      • JavaScript
    • System Design & Architecture

      • Red Hat architecture and design patterns
      • Microservices
      • Event-Driven Architecture
      • Databases
    • Developer Productivity

      • Developer productivity
      • Developer Tools
      • GitOps
    • Automated Data Processing

      • AI/ML
      • Data Science
      • Apache Kafka on Kubernetes
    • Platform Engineering

      • DevOps
      • DevSecOps
      • Ansible automation for applications and services
    • Secure Development & Architectures

      • Security
      • Secure coding
  • Learn

    Featured

    • Kubernetes & Cloud Native
      Openshift icon
    • Linux
      Rhel icon
    • Automation
      Ansible cloud icon
    • AI/ML
      AI/ML Icon
    • View All Learning Resources

    E-Books

    • GitOps Cookbook
    • Podman in Action
    • Kubernetes Operators
    • The Path to GitOps
    • View All E-books

    Cheat Sheets

    • Linux Commands
    • Bash Commands
    • Git
    • systemd Commands
    • View All Cheat Sheets

    Documentation

    • Product Documentation
    • API Catalog
    • Legacy Documentation
  • Developer Sandbox

    Developer Sandbox

    • Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new, no-cost sandbox environments.
    • Explore Developer Sandbox

    Featured Developer Sandbox activities

    • Get started with your Developer Sandbox
    • OpenShift virtualization and application modernization using the Developer Sandbox
    • Explore all Developer Sandbox activities

    Ready to start developing apps?

    • Try at no cost
  • Blog
  • Events
  • Videos

Enabling SAML-based SSO with Remote EJB through Picketlink

 

January 3, 2018
Siddhartha De
Related topics:
JavaSecurity
Related products:
Red Hat JBoss Enterprise Application Platform

Share:

    Lets suppose that you have a remote Enterprise JavaBeans (EJB) application where the EJB client is a service pack (SP) application in a Security Assertion Markup Language (SAML) architecture. You would like your remote EJB to be authenticated using same assertion which was used for SP.

    Before proceeding with this tutorial, you should have a basic understanding of EJB and Picketlink.

    I have developed a POC based on Picketlink. Below are the things I have done to achieve it.
    •  Set Picketlink to sign response and assertion in identity provider (IDP) application.
      Configure:
      `SAML2SignatureGenerationHandler` like the following in picketlink.xml of IDP application.
        <Handler class="org.picketlink.identity.federation.web.handlers.saml2.SAML2SignatureGenerationHandler">
             <Option Key="SIGN_RESPONSE_AND_ASSERTION" Value="true"/>
         </Handler>
    • Set picketlink to store SAML assertion in http-session in SP application.
      Configure:
      `SAML2AuthenticationHandler`  like the following in picketlink.xml of SP application.
        <Handler class="org.picketlink.identity.federation.web.handlers.saml2.SAML2AuthenticationHandler">
             <Option Key="ASSERTION_SESSION_ATTRIBUTE_NAME" Value="org.picketlink.sp.assertion"/>
         </Handler>
    •  Configure the sp security-domain something like below setting flag "sufficient" for both the login module and for the IDP application. You can configure your customized login module or you can use any login module available in picketbox.
          <security-domain name="sp" cache-type="default">
             <authentication>
                <login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2LoginModule" flag="sufficient" />
                <login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="sufficient">
                     <module-option name="roleKey" value="Role"/>
                     <module-option name="localValidation" value="true"/>
                     <module-option name="localValidationSecurityDomain" value="sp"/>
                </login-module>
              </authentication>
           </security-domain>
    •  In your servlet (EJB client/SP application) you need to get the signed assertion and send it along with the EJB invocation for verification like below. Here, I have used ejb-remote application which is available in quickstart [1].
    //Getting Signed SAML Assertion
    public String getSignedAssertion(HttpServletRequest httpRequest) throws Exception {
             HttpSession session = httpRequest.getSession();
             String cachedSignedAssertion = (String) session.getAttribute("org.picketlink.sp.assertion.signed");
             if (cachedSignedAssertion == null) {
                 Document assertion = (Document) session.getAttribute("org.picketlink.sp.assertion");
                 String stringSignedAssertion = DocumentUtil.asString(assertion);
                 System.out.println(stringSignedAssertion);
                 return stringSignedAssertion;
             } else {
                 System.out.println("...cached assertion...");
                 return cachedSignedAssertion;
             }
         }
     
    //EJB invocation
    public void getInitialContext(String assertion, String username) throws Exception, NamingException {
     
             Properties props = new Properties();
             props.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false");
             props.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
             props.put("remote.connections", "default");
             props.put("remote.connection.default.port", "4447");
             props.put("remote.connection.default.host", "10.10.10.10");
             System.out.println("Connecting...");
             props.put("remote.connection.default.username", username);
             props.put("remote.connection.default.password", assertion);
             props.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT","false");
             props.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS","false");
             Context context = new InitialContext(props);
             RemoteCounter aa = (RemoteCounter) context.lookup("ejb:/jboss-ejb-remote-server-side//CounterBean!org.jboss.as.quickstarts.ejb.remote.stateful.RemoteCounter?stateful");
             System.out.println(aa.getCount());
             aa.increment();
             System.out.println(aa.getCount());
             System.out.println("EJB Executed... using SAML assertion");
         }
    You can get the IDP and SP sample of Picketlink at [2] below:
    1.  https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x/ejb-remote
    2.  https://github.com/jboss-developer/jboss-picketlink-quickstarts

    That's it for today!


    Take advantage of your Red Hat Developers membership and download RHEL today at no cost.

    Last updated: March 23, 2023

    Recent Posts

    • Cloud bursting with confidential containers on OpenShift

    • Reach native speed with MacOS llama.cpp container inference

    • A deep dive into Apache Kafka's KRaft protocol

    • Staying ahead of artificial intelligence threats

    • Strengthen privacy and security with encrypted DNS in RHEL

    What’s up next?

     

    Red Hat Developers logo LinkedIn YouTube Twitter Facebook

    Products

    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform

    Build

    • Developer Sandbox
    • Developer Tools
    • Interactive Tutorials
    • API Catalog

    Quicklinks

    • Learning Resources
    • E-books
    • Cheat Sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site Status Dashboard
    • Report a security problem

    RED HAT DEVELOPER

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2025 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility

    Report a website issue