Skip to main content Skip to complementary content

Enabling Syncope Login Module

Once the Syncope Login Module is installed and configured, you can enable it in Talend ESB by deploying the Syncope blueprint XML file to the Talend-ESB-VA.B.C/container/deploy folder.

Here is a template of the Blueprint descriptor:

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
           xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.1.0"
           xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0">

    <jaas:config name="karaf" rank="2">
        <jaas:module className="org.apache.karaf.jaas.modules.syncope.SyncopeLoginModule"
                     flags="required">
           address=http://localhost:9080/syncope/rest
           admin.user=admin
           admin.password=password
           version=2
        </jaas:module>
    </jaas:config>

    <service interface="org.apache.karaf.jaas.modules.BackingEngineFactory">
        <bean class="org.apache.karaf.jaas.modules.syncope.SyncopeBackingEngineFactory"/>
    </service>

</blueprint>

Procedure

  1. Create a Blueprint descriptor based on the template above and configure the parameters:
    1. Configure the address property to reference your Syncope server by setting its value to ..syncope/rest.
    2. Configure the credentials to access Syncope.
  2. Verify that the Syncope Login Module is installed successfully:
    1. Get the list of available JAAS realms.
      karaf@trun> jaas:realm-list
      Index | Realm Name | Login Module Class Name
      ------+------------+---------------------------------------------------------
      1     | karaf      | org.apache.karaf.jaas.modules.syncope.SyncopeLoginModule
    2. Select JAAS Realm using JAAS realm index from previous step.
      karaf@trun> jaas:realm-manage --index 1
    3. Look up the Syncope users list.
      karaf@trun()> jaas:user-list

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!