How to use multiple Login Modules to authenticate SOAP webservice calls from different Consumers ?

Solution Unverified - Updated -

Issue

  • Currently SOAP webservice calls in JBoss EAP 6.4 are authenticated with SAML 2 tokens.
    A new webservice Consumer (SAP) is not able to generate SAML 2 tokens. In the future we would like provide the Username / Password authentication for this Consumer .

  • How to configure JBoss to support two different login modules?

  • We think that we have to create two different SOAP webservice modules with differnt url's.

Webservice module to authenticate with samltoken-authentication

jboss-web.xml:  <security-domain>samltoken-authentication</security-domain>
web.xml: <url-pattern>/services/v1/*</url-pattern>
Webservice module to authenticate with username-password-authentication
jboss-web.xml:  <security-domain>username-password-authentication</security-domain>
web.xml: <url-pattern>/services/otherUri/v1/*</url-pattern>
  • In the standalone.xml file,

<!-- Login module for samltoken-authentication --> <security-domain name="samltoken-authentication" cache-type="default"> <authentication> ... <!-- Login modul for username / password authentication --> <security-domain name="username-password-authentication" cache-type="default"> <authentication> ....
  • Is this the correct solution? Or do you know a better one?

Environment

  • Red Hat JBoss Enterprise Application Platform(EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.